Skip to main content
Glama

gui_hotkey

Destructive

Press allowlisted keyboard shortcuts for permission-gated remote GUI control, with explicit opt-in required before any key sequence is sent.

Instructions

Press an allowlisted keyboard shortcut, requires explicit GUI opt-in

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": {
      "keys": "<keys>"
    },
    "name": "gui_hotkey"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is known. The description adds useful context about the allowlist and explicit GUI opt-in requirement, but does not explain failure behavior, what the shortcut might affect, or how the allowlist is determined.

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?

The description is a single, front-loaded sentence with no filler. It is efficient, though it could be slightly more informative without becoming verbose.

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 simple one-parameter tool with annotations, the description covers the key operational prerequisite and allowlist constraint. It remains incomplete on the exact parameter format and the consequences of invoking a destructive shortcut, which are important for correct use.

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 description coverage is 0%, so the description must compensate for the single undocumented keys parameter. It only says 'keyboard shortcut' without specifying the expected format, chord syntax, or whether entries should be individual keys or combined strings.

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: pressing an allowlisted keyboard shortcut. This distinguishes it from text-entry siblings like gui_type, though it does not explicitly name or contrast with them.

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?

It states a key prerequisite (explicit GUI opt-in) and the allowlisting constraint, which tells the agent when the tool is permitted. However, it gives no guidance on when to choose this over gui_type, gui_click, or browser-based alternatives.

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