Skip to main content
Glama
mcp-cui-chrome

mcp-cui-chrome

by cuipy

按键

browser_press

Presses a specified key or key combination in the currently focused Chrome element, confirming the key name before and reporting success after.

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": {
      "key": "<key>"
    },
    "name": "browser_press"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesPlaywright 键名,例如 Enter、Control+A

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.4

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses two behavioral traits beyond the name: the key name is echoed before the action and a success indicator is shown afterward, which is real context an agent can rely on. It does not address side effects on the page, modifier handling, or what the failure indication looks like.

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, front-loaded sentences with no redundancy; the core action comes first and the reporting behavior second. The leading '通用' (general) label is mild filler but does signal that the tool is not context-restricted.

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 one-parameter tool with no output schema, the description covers the action and hints at the result ('结束后显示是否成功'), which partially substitutes for a return-value spec. It still leaves the failure case, modifier combinations, and page-level effects unaddressed, and with no annotations those gaps are unmitigated.

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 coverage is 100% and the single 'key' parameter is already documented with Playwright key-name conventions and an example ('Enter、Control+A'). The description adds no format or syntax detail beyond that, so the schema does the heavy lifting and the baseline of 3 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 states a specific verb and resource ('在当前焦点按一个键' – press one key at the current focus), which tells an agent exactly what happens. The '当前焦点' qualifier implicitly separates it from element-targeted siblings like browser_click, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Usage is only implied: the phrase '在当前焦点' tells the agent focus must already be established, but there is no explicit statement of when to choose this over browser_type (for text) or browser_click (for targeting an element). No alternatives or preconditions are spelled out.

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