Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

读取页面

browser_snapshot

Read the current Chrome page's title, URL, numbered interactive elements, and body text. Use to inspect page state before clicking or typing.

Instructions

用户要看当前 Chrome 页面时用这个。读取标题、网址、可操作元素编号和正文。若本该有的内容不在,用 browser_reload 刷新一次再读。快照若写了遮挡,先关掉那一层或按 Escape。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavior burden and does disclose the key traits: it is a read operation, it emits numbered interactive elements, and it can surface blocking overlays with a suggested remedy. It does not say whether the output is truncated for large pages or whether the tool has any side effects, which are the remaining gaps.

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?

Four short sentences, front-loaded with the trigger, then return contents, then two remedies. Every sentence carries distinct operational information with no padding or repetition.

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?

There is no output schema, so the description usefully explains what the snapshot contains and how to recover from stale or blocked states. It stops short of covering large-page behavior or output size limits, which is the only material omission for an agent calling it blind.

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 the baseline is 4. The description correctly implies no input is required and focuses instead on interpreting the result.

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 uses a specific verb + resource ('读取当前 Chrome 页面') and enumerates exactly what is returned: title, URL, interactive-element indices, and body text. That makes clear it produces a structured content read rather than an image, but it does not explicitly contrast with browser_screenshot, which is the closest sibling.

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

Usage Guidelines4/5

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

It gives a clear trigger ('用户要看当前 Chrome 页面时') and two conditional fallbacks: call browser_reload once when expected content is missing, and dismiss an overlay or press Escape when the snapshot reports one. Guidance is conditional and actionable, though no explicit 'do not use this when…' exclusion is stated.

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