Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_enable_devtools

Starts a DevTools session for a specified target ID so you can inspect, debug, and automate Microsoft Edge browser pages.

Instructions

启用DevTools会话

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "targetId": "<targetId>"
    },
    "name": "edge_enable_devtools"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetIdYes目标ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of disclosure. It says nothing about prerequisites (does a connection need to exist first?), whether the session is idempotent, whether it modifies browser state, or what a successful enable returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short phrase with no wasted words, and the action is front-loaded. Its brevity comes at the cost of substance rather than being efficient, so it does not earn a high score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a state-changing setup operation with no annotations and no output schema, yet the description omits prerequisites, side effects, and expected outcomes. For a tool that presumably must be paired with connect and target discovery, that leaves significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with targetId described as 目标ID, so the schema already documents the single parameter. The description adds no meaning beyond that, such as how to obtain a valid targetId (likely from edge_get_targets); a baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb (启用/enable) and a resource (DevTools会话), so the agent knows the general action. However, it does not say what a DevTools session is scoped to or how this differs from siblings such as edge_connect or edge_get_targets, so the boundary remains fuzzy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when this tool should be used, whether it must follow edge_connect or edge_get_targets, or what alternatives exist. The agent must infer the sequencing from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.