Skip to main content
Glama

reload

Refresh a browser tab and wait for it to load, up to 30 seconds; if loading pauses at a breakpoint or dialog, return an error immediately.

Instructions

Reloads the tab and waits for load (at most 30 s; a page that pauses at a breakpoint or opens a dialog while loading fails at once saying so). Returns the same shape as 'navigate'.

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
tab_idNoDefault: the active tab.
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses a 30-second cap, and that a breakpoint pause or a dialog during load causes immediate failure with an explanatory message. It omits other side effects a caller would care about, such as loss of unsaved form/JS state or whether POST data is resubmitted.

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

Conciseness5/5

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

A single front-loaded sentence: the action comes first, then the timing constraint and failure modes, then the return-shape note. The nested parenthetical is dense but every clause carries information.

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

Completeness4/5

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

For a two-optional-parameter tool with no annotations and no output schema, the description covers action, timeout, and failure semantics, and points to 'navigate' for the return shape. The only soft spot is that the caller must already know navigate's shape to benefit from that pointer.

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 both tab_id and instance_id documented including their defaults, so the schema already does the heavy lifting. The description adds nothing about parameter meaning, which is acceptable at this coverage level.

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 ("Reloads the tab") plus the accompanying wait-for-load behavior, so the agent knows exactly what the call does. It stops short of explicitly differentiating itself from the sibling 'navigate', relying on the reference to it for return shape rather than for contrast.

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

Usage Guidelines3/5

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

Usage is only implied: a reload is naturally used to re-fetch the current page. The description never says when to prefer this over 'navigate', nor any precondition such as there being an existing loaded page.

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