Skip to main content
Glama
Edge DevTools MCP

Edge DevTools MCP

by syunnrai123

edge_navigate

Navigate the browser to a specified URL to load pages and direct sessions for testing or automation tasks.

Instructions

导航到指定URL

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": {
      "url": "<url>"
    },
    "name": "edge_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes要导航的URL
sessionIdNo会话ID(可选)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 disclosure burden, yet it only states the navigation action. It does not say whether navigation blocks or waits for page load, what happens when no active target/session exists, whether it creates or reuses a tab, or what the caller receives.

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?

It is a single front-loaded sentence with zero filler, which is structurally clean. The brevity borders on under-specification, but nothing is wasted or buried.

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?

For a browser-automation navigation tool embedded in a family of session-based DevTools siblings, the definition omits the session/lifecycle context and any post-call behavior details. With no annotations and no output schema, the description alone leaves an agent without enough information to call it correctly 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%, with url marked required and sessionId described as optional, so the parameters are already documented. The description adds nothing beyond the schema baseline, which is acceptable but not additive.

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 single sentence '导航到指定URL' does state a concrete action (navigate) on a concrete resource (URL), so the basic purpose is legible. However, it largely restates the tool name edge_navigate and offers no differentiation from siblings such as edge_connect, edge_get_page_content, or edge_wait_for_selector, so an agent must infer its role from the name alone.

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 to use this tool versus alternatives, and no prerequisites are stated. In particular, it never says whether an existing browser session/target must be established first (e.g., via edge_connect) or when the optional sessionId should be supplied.

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