Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

后退

browser_go_back

Navigate the current Chrome tab back one page. Use it to return to the previous page in browser history and confirm whether the back navigation succeeded.

Instructions

通用:当前标签后退一页。开始前说明,结束后显示是否退回到上一页。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the two key traits that matter here — it acts on the current tab only and moves exactly one step — plus a reporting obligation after the call. It omits what happens at the start of the history stack (no-op vs. error) and whether page state is lost, which are the main failure modes an agent would need.

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?

The purpose is front-loaded in a single short clause, followed by the narration instructions. The meta-instructions ('开始前说明', '结束后显示…') add words but serve an operational purpose for the calling agent, so little 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 zero-parameter, no-output-schema tool this covers the essentials, but with no annotations to lean on it should also say what occurs when there is no prior page and how the agent should react. The described post-call reporting partially compensates.

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 disambiguate; baseline 4 applies. The schema is empty and consistent with the described behavior.

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 states a specific verb (后退/back) and resource scope (当前标签 / current tab), making it immediately distinguishable from siblings like browser_navigate or browser_reload. It stops short of naming a sibling to contrast with, so it is clear but not maximally differentiated.

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?

The '通用' prefix signals a general-purpose navigation move and the one-page scope implies when to reach for it, but there is no explicit when-not guidance, no mention of alternatives such as browser_navigate for arbitrary URLs, and no note that history position matters.

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