Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

reload_tab

Refresh the current or a specified browser tab, optionally bypassing cache for a hard refresh. Use it to update page content or clear stale cached resources.

Instructions

Reload the current or specified 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_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
ignoreCacheNoHard reload bypassing cache

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and mostly doesn't: it never says whether the call blocks until the page finishes loading, what happens if tabId is invalid or closed, or what is returned. The only behavioral hint, cache bypass, is already in the schema's ignoreCache 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 filler; the target scope leads. It is efficient, though its brevity comes at the cost of the behavioral detail noted elsewhere.

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 two-optional-parameter, non-destructive-looking action with a fully described schema, the definition is adequate to select and invoke the tool. It falls short on load-completion semantics and error behavior, which matter for an agent sequencing page interactions.

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 coverage is 100% and both parameters are documented there. The description adds only one nuance beyond the schema, that the tab defaults to the current one, so the baseline of 3 applies rather than higher credit.

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?

Names a specific verb (reload) and resource (tab) and states the target scope: 'current or specified tab'. An agent can distinguish it from close_tab, new_tab, and switch_to_tab without further reading, though there is no explicit sibling differentiation.

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: the phrase 'current or specified' signals that omitting tabId reloads the active tab. There is no statement of when to prefer this over go_back, open_url, or other navigation tools, and no exclusions or prerequisites.

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