Skip to main content
Glama

hands_press

Sends a key press or key chord such as Enter, Tab, or Control+A to the active window, letting agents perform confirmations, navigation, and shortcuts without a mouse.

Instructions

Press a key or chord, e.g. 'Enter', 'Tab', 'Escape', 'Control+A'.

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": "hands_press"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It mentions chords, which implies modifier support, but does not disclose where the key event is sent, whether focus is required, what element receives the input, or what happens on failure.

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?

The definition is one front-loaded sentence with zero wasted wording. The examples are compact and directly useful for understanding the expected input format.

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?

Although the tool is simple with only one parameter and no output schema, the absence of annotations means the description should explain more about keyboard targeting and side effects. Key behavioral context such as focus requirements and event dispatch is missing.

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 0%, so the description must compensate for the single 'key' parameter. Its examples do add useful format meaning, including chord syntax like 'Control+A', but they do not enumerate accepted key names or clarify case sensitivity.

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 and resource: 'Press a key or chord', with concrete examples such as 'Enter', 'Tab', and 'Control+A'. It is immediately clear what the tool does, but it does not distinguish itself from sibling tools like hands_type or hands_click.

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?

The description provides no explicit guidance on when to use this tool versus alternatives such as hands_type for text input or hands_click for pointer actions. The examples imply keyboard input but do not establish boundaries or exclusions.

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