PhantomHand

by SilenceEchoLab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

browser_press_key

Press special keys such as Enter, Tab, Escape, or Backspace to simulate keyboard actions for browser control.

Instructions

Press a special key (e.g., Enter, Tab, Escape, Backspace).

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

Input Schema

Name	Required	Description	Default
`key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jul 5, 2026

TDQS

B3.3/5.0

Behavior2/5

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

The description does not disclose behavioral details beyond pressing a key. There are no annotations to supplement. It does not state whether the key is pressed and released, or if it can be held, or what happens if an invalid key is provided.

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?

Single sentence that conveys the essential information without extraneous words. Front-loaded with the action and examples.

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?

Given the tool's simplicity (one param, no output schema, no annotations), the description is minimally viable. It covers the purpose but lacks differentiation from siblings and behavioral details. For a simple tool, it meets the basic need but has gaps.

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 has 0% description coverage for the key parameter. The tool description adds meaning by listing example keys and stating 'special key', which provides context beyond the raw string type. However, it does not specify the full set of acceptable keys or format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Press a special key') and provides specific examples (Enter, Tab, Escape, Backspace), making it clear what the tool does. It distinguishes itself from siblings like browser_type and browser_keyboard_shortcut.

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 alternatives. Does not specify what constitutes a 'special key' or when to use browser_type or browser_keyboard_shortcut instead. The description implies usage for pressing a single non-character key, but this is not explicit.

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