Skip to main content
Glama

desktop_key_up

Release a held keyboard key or modifier to complete desktop automation actions. It fails closed in stateless mode, so use a press action instead.

Instructions

agent-desktop key-up: Release a held key or modifier (fails closed in stateless mode; use press)

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

Input Schema

NameRequiredDescriptionDefault
comboYesKey or modifier to hold/release: shift, meta, ctrl ... (cmd is accepted); the command is rejected in stateless mode, use press instead
forceNoSend the combo even if the adapter flags it as a dangerous shortcut

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/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 that the tool fails closed in stateless mode, which is genuine behavioral context, but says nothing about what a failure looks like, whether releasing an unheld key errors, or what the response contains.

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 sentence with the operative behavior front-loaded and the caveat in a parenthetical. The 'agent-desktop key-up:' prefix is redundant with the tool name but costs little.

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 two-parameter release tool with full schema coverage and no output schema, this is close to adequate. It still omits the pairing contract with desktop_key_down and any failure/return behavior, which matter for an agent composing key sequences.

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%, and the schema's 'combo' description already contains the same stateless-mode/use-press caveat found in the tool description. The description therefore adds no parameter meaning beyond the structured fields; baseline 3 applies.

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: 'Release a held key or modifier.' By naming it 'key-up' and describing release of a *held* key, it implicitly pairs with desktop_key_down, but it never names that sibling explicitly as the counterpart operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete conditional alternative: 'fails closed in stateless mode; use press' — telling the agent when this tool will not work and which tool to use instead. No guidance about ordering with desktop_key_down or batch use.

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