Skip to main content
Glama

hotkey

Send key combinations to desktop GUI applications, with dry-run mode to preview the action before execution.

Instructions

Press a hotkey chord, e.g. 'ctrl+a' or 'alt+F4'.

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": {
      "combo": "<combo>"
    },
    "name": "hotkey"
  }
}

Input Schema

NameRequiredDescriptionDefault
comboYes
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and largely drops it. Most importantly it never discloses that dry_run defaults to true, so a reader of the description would reasonably assume the chord is actually sent; it also says nothing about which application receives the keystrokes, whether modifiers are held correctly, 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.

Conciseness4/5

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

One short sentence, front-loaded with the verb and immediately backed by illustrative examples; nothing is redundant. It is efficient rather than padded, though the brevity is achieved partly by omitting information the tool genuinely needs.

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 a mutation-style tool with no annotations, no output schema, and 0% schema coverage, the description should explain the dry_run default, focus requirements, and the effect of a successful press. None of that is present, so an agent can invoke this tool while misunderstanding whether it actually types anything.

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. The examples ('ctrl+a', 'alt+F4') do add real meaning for the required combo parameter beyond a bare string type, but the second parameter, dry_run, is never mentioned despite its non-obvious default of true, which is the single most consequential semantic here.

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 and resource ('Press a hotkey chord') and supplies two concrete chord examples, so the agent knows exactly what operation this performs. It does not, however, distinguish this from keystroke-adjacent siblings like type_text or click, leaving the agent to infer the boundary from names alone.

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?

There is no when-to-use guidance at all: no statement about when a hotkey is preferable to type_text or click, no prerequisites such as which window must be focused, and no exclusions. The examples clarify syntax only, not tool selection.

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