format

Author: wolfib

docs/third-party-developer-tools.md

@@ -14,7 +14,7 @@ Chrome DevTools for Agents uses an event-based mechanism to discover tools expos
 2.  **Listener:** Your application listens for this event and provides the tool definitions.
 3.  **Response:** Your application must call `event.respondWith()` to register a `ToolGroup` object.
 
-*Note: Chrome DevTools for Agents requests this list automatically after page navigations (e.g., `new_page`, `navigate_page`) or when explicitly requested via the `list_3p_developer_tools()` MCP tool.*
+_Note: Chrome DevTools for Agents requests this list automatically after page navigations (e.g., `new_page`, `navigate_page`) or when explicitly requested via the `list_3p_developer_tools()` MCP tool._
 
 ## Implementation
 
@@ -24,7 +24,7 @@ To expose tools, implement a listener for the `devtoolstooldiscovery` event and
 
 Your tools must follow the `ToolDefinition` and `ToolGroup` interfaces:
 
-``` typescript
+```typescript
 export interface ToolDefinition {
   name: string;
   description: string;
@@ -37,50 +37,51 @@ export interface ToolGroup {
   description: string;
   tools: ToolDefinition[];
 }
-
 ```
 
 ### Example Implementation
 
-``` typescript
-window.addEventListener('devtoolstooldiscovery', (event: DevtoolsToolDiscoveryEvent) => {
-  event.respondWith({
-    name: 'Page-specific DevTools',
-    description: 'Provide runtime info directly from the page\'s JavaScript',
-    tools: [
-      {
-        name: 'add',
-        description: 'Calculates the sum of two numbers.',
-        inputSchema: {
-          type: 'object',
-          properties: {
-            a: { type: 'number' },
-            b: { type: 'number' },
+```typescript
+window.addEventListener(
+  'devtoolstooldiscovery',
+  (event: DevtoolsToolDiscoveryEvent) => {
+    event.respondWith({
+      name: 'Page-specific DevTools',
+      description: "Provide runtime info directly from the page's JavaScript",
+      tools: [
+        {
+          name: 'add',
+          description: 'Calculates the sum of two numbers.',
+          inputSchema: {
+            type: 'object',
+            properties: {
+              a: {type: 'number'},
+              b: {type: 'number'},
+            },
+            required: ['a', 'b'],
+          },
+          execute: async (input: {a: number; b: number}) => {
+            return input.a + input.b;
           },
-          required: ['a', 'b'],
         },
-        execute: async (input: {a: number, b: number}) => {
-          return input.a + input.b;
-        }
-      }
-    ]
-  });
-});
-
+      ],
+    });
+  },
+);
 ```
 
 ## Tool Invocation
 
 Once discovered, MCP clients can execute your tools through Chrome DevTools for Agents using:
 
-  * **`execute_3p_developer_tool`**: The standard way to invoke a specific registered tool by name with validated parameters.
-  * **`evaluate_script`**: Allows for more complex interactions by running a custom script that calls `window.__dtmcp.executeTool()` directly, enabling you to compose functionality.
+- **`execute_3p_developer_tool`**: The standard way to invoke a specific registered tool by name with validated parameters.
+- **`evaluate_script`**: Allows for more complex interactions by running a custom script that calls `window.__dtmcp.executeTool()` directly, enabling you to compose functionality.
 
 ## Important Considerations
 
-  * **Experimental Status:** This feature is currently experimental. APIs may change, and there are no guarantees regarding stability.
-  * **Security & Scope:**
-      * **Context:** Third-party developer tools execute only within the context of the page that defines them. They do not persist across origins.
-      * **Capabilities:** These tools do not grant expanded privileges; they can only execute code that an attacker would already be able to run on that page.
-  * **DOM Elements:** If your tools require DOM elements as inputs or outputs, they are handled via special UIDs referenced in the accessibility tree.
-  * **Flags:** The implementation is gated behind the `--categoryExperimentalThirdParty=true` command-line flag.
+- **Experimental Status:** This feature is currently experimental. APIs may change, and there are no guarantees regarding stability.
+- **Security & Scope:**
+  - **Context:** Third-party developer tools execute only within the context of the page that defines them. They do not persist across origins.
+  - **Capabilities:** These tools do not grant expanded privileges; they can only execute code that an attacker would already be able to run on that page.
+- **DOM Elements:** If your tools require DOM elements as inputs or outputs, they are handled via special UIDs referenced in the accessibility tree.
+- **Flags:** The implementation is gated behind the `--categoryExperimentalThirdParty=true` command-line flag.