spectra-mcp

Overview Schema Source Related Servers Discussions Admin

browser_reload

Reload a browser session and return updated page observations as none, compact, or full snapshots for continued web automation.

Instructions

Reload and return no, compact, or full snapshot observation.

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

Input Schema

Name	Required	Default
`observe`	No	compact
`session_id`	No
`timeout_ms`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.4/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 burden. It hints that a snapshot is produced after reloading, but does not disclose that a reload discards page state, what session_id is needed, or how timeout_ms affects behavior.

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

Conciseness3/5

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

A single short sentence with no filler, which is good, but the phrasing 'return no, compact, or full snapshot observation' is grammatically garbled and slightly obscures the intent.

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?

An output schema exists so return values needn't be explained, but with zero annotations and zero schema descriptions the definition leaves the mutation semantics, session targeting, and observe-mode tradeoffs unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters. The description only restates the observe enum values ('no, compact, full') without explaining the tradeoff between them, and gives no meaning for session_id or timeout_ms.

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?

States the verb 'reload' and mentions returning a snapshot observation, so the action is identifiable, but the wording 'return no, compact, or full snapshot observation' is awkward and the resource (the current page of a session) is only implied. No differentiation from siblings like browser_navigate or browser_snapshot.

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: nothing says when to reload versus navigate to a URL or call browser_snapshot instead. The relationship to the sibling observation tools is left entirely to inference.

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