Simulate keyboard key presses like Enter, Escape, Tab, or Arrow keys in automated Chrome/Chromium sessions to trigger form submissions, navigation, and UI actions.
Press a keyboard key (e.g. Enter, Escape, Tab, Backspace, ArrowDown, ArrowUp, Space).
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Key name (Enter, Escape, Tab, Backspace, etc.) |
Changes observed during successful MCP inspections.
v0.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether the key is sent to the focused element, whether it can trigger destructive default actions (e.g., Enter on a form), or any focus/permission requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted words. It states the action and examples immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema or annotations, the description is adequate for basic invocation but omits important context about focus target and side effects. It is minimally viable rather than fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single parameter is fully documented in the schema. The description adds a few more example key names, but they are largely redundant with the schema's 'etc.' and do not add syntax or constraint details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Press') and resource ('keyboard key'), and gives concrete key examples. It is clearly distinct from sibling tools like browser_click or browser_fill, but does not explicitly name or route against them, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no when-to-use guidance, prerequisites, or alternatives. It does not explain when to prefer key presses over browser_fill, browser_click, or browser_mouse, leaving usage entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.