Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

刷新页面

browser_reload

Reloads the current browser tab, equivalent to pressing F5. Use it once when expected buttons or content are missing from a snapshot, then read the page again.

Instructions

通用:刷新当前标签,相当于 F5。快照里本该出现的按钮或正文没有时用一次,然后再读页面。不要连续反复刷新。

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It discloses the F5 equivalence and warns against repeated reloading, which is useful, but it never says whether reload discards form/scroll state or whether it returns after the page finishes loading — meaningful gaps for a browser mutation.

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?

Three short sentences: what it is, when to use it, and what not to do. The action identity is front-loaded and no sentence is filler.

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 zero-parameter browser action with no output schema, the definition covers purpose, trigger, and the anti-pattern. Only the post-reload state effects (lost inputs, load-wait semantics) are left unstated, which is a minor gap given the tool's simplicity.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to explain beyond what the empty schema already conveys. Baseline of 4 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 names a specific action and target ('刷新当前标签') and anchors it with a familiar equivalence ('相当于 F5'), so there is no ambiguity about what the tool does. It does not explicitly contrast itself with siblings like browser_navigate or browser_go_back, which is the only thing separating it from a 5.

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

Usage Guidelines5/5

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

It gives a concrete trigger condition ('快照里本该出现的按钮或正文没有时用一次') plus a required follow-up step ('然后再读页面'), and an explicit when-not ('不要连续反复刷新'). This is a complete use/no-use rule rather than an implied one.

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