Skip to main content
Glama

key_tap

Simulates a single keyboard key tap by name in the frontmost window, enabling AI agents to press keys in games or keyboard-controlled apps with adjustable hold time.

Instructions

Tap a raw keyboard key by name (e.g. 'return', 'w', 'esc').

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

Input Schema

NameRequiredDescriptionDefault
keyYes
hold_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and supplies almost none: it does not say whether the call is blocking, which application receives the key, whether press and release are atomic, or that hold_ms controls a default 120ms hold. Only the notion of a discrete tap is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the verb and resource, with an inline example list. Zero waste, though the brevity is close to under-specification rather than deliberate economy.

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?

For an input-injection tool with no annotations and no output schema, the definition should explain hold duration, blocking behavior, and targeting. It covers only the key-name format, leaving an agent able to guess intent but not to call the tool with informed expectations.

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?

Schema coverage is 0%, so the description must compensate. It adds useful meaning for 'key' via name examples, but says nothing about 'hold_ms', which is undocumented in both schema and description — a meaningful gap for a timing parameter with a default.

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?

States a specific verb ('Tap') and resource ('raw keyboard key') and gives concrete key-name examples ('return', 'w', 'esc'). The word 'tap' also implies a press-and-release, which implicitly separates it from key_down/key_up, but it never names or contrasts those siblings explicitly.

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 when-to-use or when-not-to-use guidance. An agent must infer that 'tap' is the quick-press alternative to key_down/key_up, combo, or press, and nothing in the description confirms that reasoning or states prerequisites such as target-window focus.

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