Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_connect

Connects to or launches Microsoft Edge through a remote debugging port for browser automation. Use it to start DevTools protocol sessions for navigation, DOM inspection, screenshots, and network monitoring.

Instructions

连接到Edge浏览器

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "edge_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo远程调试端口
headlessNo是否以无头模式运行
browserPathNoEdge浏览器可执行文件路径

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing. It does not say whether connecting launches a new browser process (a real side effect), whether an existing session is reused, what happens on port conflict, whether the connection persists, or what a successful call returns. For a tool whose whole job is establishing state that later calls depend on, this is a major gap.

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

Conciseness4/5

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

A single short clause with zero filler and no tangential content. Its brevity is clean rather than padded, though it sits close to the edge of under-specification rather than genuine conciseness.

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?

The tool has three optional parameters, no annotations, and no output schema, so the description must explain setup semantics on its own. It fails to state the preconditions for later edge_* calls, whether a browser is launched or attached to, or what the agent should do with the result, leaving an agent unable to call it confidently in context.

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 description coverage is 100%, so port, headless, and browserPath are already documented in the input schema (remote debugging port, headless mode, executable path). The description adds no meaning beyond the verb itself, which is acceptable given the schema does the work, but baseline 3 is the ceiling.

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

Purpose4/5

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

"连接到Edge浏览器" names a specific verb (connect) and resource (Edge browser), so an agent knows what it does. It offers no differentiation from siblings such as edge_disconnect or edge_enable_devtools, leaving the agent to infer the relationship between connecting and enabling DevTools.

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

Usage Guidelines4/5

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

The description supplies no explicit when-to-use guidance, no prerequisites, and no alternatives. It does not say whether this must be called before the other edge_* tools, whether it attaches to an already-running instance or launches a new one, or when to prefer edge_disconnect. In practice the verb "connect" implies a setup step, but nothing in the text confirms that inference.

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