Skip to main content
Glama

reload_page

Reload the active browser page to refresh content or retest responsive layouts; configure wait conditions and timeout for controlled inspection.

Instructions

Reload the currently active page in the browser.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNoTimeout in ms (default: 30000ms).
wait_untilNoWait condition on reload (default: "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 provided, so the description bears the full behavioral burden, yet it discloses none of the consequences of a reload: loss of unsaved form/JS state, what happens if no page is active, or whether the call errors. The wait_until parameter hints that the call blocks until a condition, but the description never confirms this or explains the default waiting behavior.

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 zero filler, appropriately sized for a two-parameter tool whose schema is fully documented. It could add one clause of useful context without becoming bloated, but nothing present is wasted.

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?

For a simple reload tool with a fully documented schema and no output schema, the definition is minimally sufficient to invoke correctly. It is incomplete on the things an agent most needs to reason about — state destruction and failure modes when no page is active — which annotations would normally cover but here are absent.

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%: both timeout and wait_until carry descriptions, and the enum values are enumerated. The description adds no semantics beyond that, so the baseline 3 applies.

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 plus resource: "Reload the currently active page in the browser." That verb distinguishes it from navigation siblings like open_page, navigate_back, and navigate_forward without needing to name them, since those act on history or new targets rather than the loaded page.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. "Currently active page" weakly implies it acts on an existing page rather than opening one, but an agent must infer for itself whether to reload versus calling open_page or a navigation tool.

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