Skip to main content
Glama

desktop_press

Sends key combinations such as Return, Escape, Cmd+C, or Shift+Tab to a target app or window, optionally without focusing it, to automate desktop shortcuts.

Instructions

agent-desktop press: Send a key combo: return, escape, cmd+c, shift+tab ...

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

Input Schema

NameRequiredDescriptionDefault
appNoTarget application name; keys go to its process without focusing it (--headed focuses its window first)
comboYesKey combo: return, escape, cmd+c, shift+tab ...
forceNoSend the combo even if the adapter flags it as a dangerous shortcut
window_idNoTarget the application instance that owns this window (from list-windows); use it when several instances share one name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden, yet it discloses nothing about behavior: it does not say the combo goes to the focused app by default, whether the call blocks until delivery, what happens on failure, or that a dangerous-shortcut guard can block it. Those facts exist only in the schema parameter text.

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

Conciseness3/5

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

It is a single short sentence with no padding, and the essential content is front-loaded, but the 'agent-desktop press:' prefix is redundant with the tool name and the remaining content is too sparse to be genuinely useful.

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 4-parameter action tool with no annotations and no output schema, the description is far too thin. It leaves out the safety guard behavior, targeting semantics, and any indication of what the call returns or how errors surface.

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 100%, so the baseline is 3. The description only re-states the combo format already documented in the schema and adds no meaning for app, force, or window_id.

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 gives a specific verb and resource ('Send a key combo') plus concrete examples (return, escape, cmd+c, shift+tab), so an agent knows exactly what the tool does. It does not differentiate from siblings like desktop_key_down/desktop_key_up, which is the main ambiguity left.

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 guidance on when to use this versus alternatives such as key_down/key_up for held modifiers, or batch for sequences. No prerequisites (target app focus, permissions) are stated.

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