Skip to main content
Glama

key_down

Holds a keyboard key down to simulate continuous input for sustained actions until released or automatically time-capped for safety.

Instructions

Hold a raw key down until key_up or the hard cap releases it.

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

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/5.0
Behavior2/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 cross-call state (the key stays down after the call returns) and the existence of a timeout safety cap, but it omits whether OS-level input permissions are required, what happens for unrecognized key names, and how long the cap actually is — significant gaps for an input-synthesis tool.

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?

One short, well-formed sentence with no filler, front-loading the action and the release condition. Nothing is redundant.

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, no-output tool the description covers the essential lifecycle, which is the most important thing an agent needs. However, with zero annotation and zero schema coverage, the missing key-name format and error/permission behavior leave the agent guessing on the one input it must supply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter ('key') at 0% schema description coverage, and the description adds no format guidance at all — no examples of accepted key names ('a', 'shift', 'f1'), no case sensitivity, no modifier handling. The single sentence spends its words on lifecycle rather than telling the caller what to put in the argument.

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 ('Hold a raw key down') and names the exact termination conditions ('until key_up or the hard cap'). It effectively distinguishes the tool from key_tap (a tap that self-releases) by making the caller responsible for release, though it never names key_tap explicitly.

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 agent must infer that key_up is needed to end the hold and that key_tap is the alternative for a one-shot press. There is no explicit when-to-use versus when-not-to-use statement, and the duration of the 'hard cap' is left unspecified.

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