Skip to main content
Glama

release_all

Releases every held key immediately as a panic button, stopping unintended or stuck input during game or app control.

Instructions

Panic button: release every held key immediately.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "release_all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the mutation (held keys are released) and the timing (immediate), which is the core behavior for a 0-parameter tool, but it says nothing about idempotency when nothing is held, whether it returns the released keys, or whether it also clears held mouse buttons or sticks.

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

Conciseness5/5

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

A single short sentence with the trigger framing first and the effect second. Every word earns its place, with no preamble or restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 0-param, no-output-schema action tool this is nearly complete: the agent knows what it does and that it should be treated as an emergency action. Only the interaction with non-key state (mouse buttons, sticks) and the post-call state are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a 0-param tool applies. Nothing is missing or misleading on this dimension.

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?

"Release every held key" is a specific verb+resource, and the qualifier "every" separates it from the single-key sibling key_up. The "Panic button" framing also tells the agent this is the catch-all escape action, though no sibling is named explicitly.

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?

"Panic button" plus "immediately" implies the use case (emergency stop when input state must be cleared), but there is no explicit statement of when to prefer this over key_up or press, nor any exclusion of normal, non-emergency release flows.

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