Skip to main content
Glama
Sign In
edge-mcp

edge-mcp

by hualang-C
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

reload

Refresh the active Edge browser tab and optionally wait for load, DOMContentLoaded, or network-idle conditions before continuing automation.

Instructions

Reload the active tab.

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": "reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitUntilNoWhen to consider navigation finished: load (default), domcontentloaded, networkidle0 (500ms no requests), networkidle2 (500ms with <=2 requests)load

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 disclosure burden, yet it says nothing about what happens if no tab is active, whether it errors, whether it preserves scroll/form state, or whether it blocks until load completes. The waitUntil parameter hints at navigation-wait behavior, but that information lives in the schema, not the description.

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 front-loaded sentence with no wasted wording. It is arguably too terse for a browser automation tool, but there is no filler or redundancy.

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 (one optional enum param, no output schema, no annotations), so a short description is defensible. However, it omits what happens with no active tab and whether the call returns after full load, which are relevant for an agent orchestrating browser actions.

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%, and the single waitUntil enum is thoroughly documented in the schema, so the baseline of 3 applies. The description adds nothing about how waitUntil interacts with reload.

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?

States a specific verb and resource ("Reload the active tab"), which is clearly distinct from siblings like navigate, go_back, and go_forward. It stops short of explicitly contrasting itself with navigate, but the action is unambiguous.

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 gives no when-to-use guidance and no mention of alternatives, even though navigate to the current URL is a plausible substitute. The agent must infer that reload re-fetches without changing the URL and that it applies only to the active tab.

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

Deploy Server

Other Tools