Skip to main content
Glama

key_up

Releases a previously held raw keyboard key to stop stuck or repeated input. Use it to end a key hold and restore normal typing or gameplay.

Instructions

Release a raw key held by key_down.

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

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the entire behavioral burden. It conveys that this is a state-releasing call, but says nothing about error behavior for unheld keys, whether it is idempotent, whether it affects other held keys, or what state the input is left in — significant gaps for an input-injection tool with zero annotation coverage.

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 short sentence with no filler, and the verb is front-loaded so the agent sees the action immediately. Its terseness contributes to the gaps noted elsewhere, but there is no wasted wording.

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?

With no annotations, no output schema, and an undocumented parameter, the description is the only source of behavioral information and it supplies just one sentence. For a state-affecting input tool it should at minimum describe the key format and the result of releasing a key that isn't held.

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% for the single required "key" parameter, so the description must compensate. The phrase "raw key" hints that the value is a low-level key identifier rather than a character or action name, but it provides no format, casing, or example values, leaving the parameter largely undefined.

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+resource pair ("Release a raw key") and ties it to the sibling counterpart key_down, which distinguishes it from key_tap and press. It doesn't explicitly contrast with release_all or phrase the operation's scope beyond the key_down link, so it stops short of full sibling differentiation.

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?

Usage is implied by the reference to key_down: an agent can infer this is the paired teardown call. However, there is no explicit when-to-use clause, no mention of release_all as the alternative for bulk cleanup, and no statement about prerequisites or what happens if the key was never pressed.

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