Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

标签页

browser_tabs

List, open, switch, or close browser tabs to manage multiple pages in one Chrome session. Specify an action and optional URL or tab index to control tabs directly.

Instructions

通用:列出、新建、切换或关闭标签。开始前说明要做什么,结束后说明是否成功。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "browser_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNonew 时可选,新建后立刻打开的地址
indexNoswitch 或 close 的标签序号,从 0 开始
actionYeslist、new、switch 或 close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about whether closing a tab is destructive, what happens to the closed tab's state, whether index shifts after a close, or what a list returns. The announced meta-ritual ('say what you'll do, then say if it worked') is process guidance, not behavioral information about the tool.

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?

Two short sentences, with the operation list front-loaded so the agent learns the scope immediately. The second sentence is redundant boilerplate about narration rather than tool knowledge, which costs it a point but the text is far from bloated.

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?

A three-parameter tool covering a destructive operation (close) with no annotations and no output schema needs the description to cover safety and return behavior, and it does neither. An agent cannot tell from this text whether closing a tab loses unsaved state or what a list call yields.

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 url and index already documented per-action in the schema, so the baseline of 3 applies. The description adds nothing beyond the schema — for example it does not clarify that index is interpreted in the post-close ordering or whether url is ignored for non-new actions.

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 resource (tabs) with four concrete operations (list/new/switch/close) that map directly to the action enum, so an agent can tell this apart from page-level siblings like browser_navigate or browser_click. The '通用' framing makes clear it is a multi-action tab-management tool rather than a single verb.

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?

No guidance on when to use this tool versus browser_navigate (new tab vs navigate current page), or versus browser_close. The only usage-adjacent content is a workflow instruction to announce the action before and after, which does not help select between tools.

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