Hold keyboard keys down for a set duration (max 10 seconds) to enable key repeat or game controls. Use for automated X11 desktop interactions.
Hold key(s) down for seconds (max 10), e.g. for games or key repeat.
| Name | Required | Description | Default |
|---|---|---|---|
| combo | Yes | ||
| seconds | Yes | ||
| screenshot_after | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the max duration (10 seconds) and implies automatic release after the given seconds, but does not explain failure modes, interruption behavior, or required permissions.
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 that includes the key constraint (max 10 seconds) and a usage example without any wasted words.
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?
Given no annotations, no output schema, and 0% schema coverage for three parameters, the description is incomplete. It omits any explanation of `screenshot_after` and does not clarify whether keys are released automatically or what happens if the hold is interrupted.
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 0%, so the description must compensate for all three parameters. It clarifies `seconds` (with a max of 10) and implies `combo` means key(s), but never mentions `screenshot_after`, leaving one parameter completely undocumented.
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 action (hold key(s) down) and the duration parameter. Distinguishes from the sibling `key` implicitly by emphasizing holding rather than pressing, but does not explicitly name the alternative tool.
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?
Provides example contexts ('for games or key repeat') which imply when to use it, but does not explicitly compare with the sibling `key` or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.