Skip to main content
Glama

gc_controller_release

Releases a held button on a specified GameCube controller port, letting you stop simulated or hardware button input at the right time.

Instructions

Release a button on a GameCube controller port.

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": {
      "instance_id": "<instance_id>",
      "port": "<port>",
      "button": "<button>"
    },
    "name": "gc_controller_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
buttonYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never says what happens if the button was not pressed, whether the release is idempotent, whether it errors on an invalid port or button name, or whether it affects only the given instance. For a state-mutating input tool this is a substantial gap.

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 front-loaded sentence with zero filler and the verb first. It is efficient, though its brevity is under-specification rather than disciplined conciseness.

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 three required parameters, no annotations, no output schema, and no parameter documentation, the definition leaves the agent guessing about identifier format, button vocabulary, and failure behavior. A sentence on button naming and the press/release pairing would close most of the gap.

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 all three parameters (instance_id, port, button) are undocumented in structured fields. The description only gestures at 'port' and 'button' and says nothing about instance_id, valid port ranges, or acceptable button names, so it does not compensate for the coverage gap.

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 ('Release') and resource ('a button on a GameCube controller port'), so the agent knows exactly what state change is being requested. It does not explicitly distinguish itself from siblings like gc_controller_press or gc_controller_press_once, which is the only thing keeping it from a 5.

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 when-to-use guidance, no mention that this is the counterpart to a hold-style press, and no exclusions or alternatives named. The agent must infer the press/release pairing from the sibling names alone, which the definition does not leverage.

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