Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_disconnect

Disconnects from the Microsoft Edge browser to end the DevTools session and stop browser control.

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_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 almost nothing beyond the action itself. It does not say whether the browser process is closed or merely detached, whether the session/state is destroyed, whether an active debugging session is interrupted, or whether the call is safe to repeat. For a teardown operation with zero annotation coverage this is a meaningful 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 phrase with zero filler and the action front-loaded, so it is efficient and easy to scan. The brevity is close to under-specification rather than verbosity, which is penalized in other dimensions rather than here.

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

Completeness3/5

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

The tool is simple (no parameters, no nested objects, no output schema), so the bar for completeness is low and the one-line description roughly meets it. However, with no annotations and no statement of what disconnecting actually does to the browser session or to subsequent calls, an agent cannot fully anticipate the consequences of calling it.

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

Parameters4/5

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

The tool takes no parameters and the schema is an empty object, so there is nothing for the description to clarify. Per the zero-parameter baseline this scores 4; a 5 would require the description to add some other useful calling context, which it does not.

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?

The description gives a specific verb+resource: '断开' (disconnect) applied to 'Edge浏览器' (Edge browser). That verb naturally contrasts with the sibling edge_connect, so an agent can distinguish the two without reading either schema. It stops short of 5 because no scope or effect details accompany the verb.

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?

The description contains no when-to-use or when-not-to-use guidance and no mention of alternatives. The usage is strongly implied by the verb (call it to tear down a connection established by edge_connect), but the definition itself states nothing about sequencing, preconditions, or whether a connection must exist first.

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