Skip to main content
Glama

gc_controller_reset

Reset a specified GameCube controller port to its neutral state, clearing stuck or unintended input for a selected emulator instance.

Instructions

Reset a GameCube controller port to its neutral state.

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>"
    },
    "name": "gc_controller_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
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?

With no annotations, the description carries the full burden. It does disclose the outcome (all inputs go to neutral), but says nothing about whether held buttons/sticks are cleared simultaneously, how this interacts with a running sequence, what happens on an invalid instance or out-of-range port, or whether the call is idempotent.

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 no filler or redundant phrasing. Its brevity is clean, though it leaves too much unsaid for a two-required-parameter tool.

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 state-mutating hardware tool with no annotations, no output schema, and zero schema description coverage, the definition should cover at minimum valid port values, instance requirements, and the absence of a meaningful return value. None of that is present.

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 coverage is 0%: neither 'instance_id' nor 'port' is documented in the schema, and the description only vaguely alludes to a port without giving valid ranges (e.g., which port indices are supported) or explaining the instance identifier. The description fails to 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 ('Reset') and resource ('a GameCube controller port') plus the resulting state ('neutral'), which is more informative than a bare restatement. It doesn't explicitly differentiate itself from near-siblings like gc_controller_release, so it stops short of 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 guidance on when to prefer this over gc_controller_release or gc_controller_press_once, nor any stated prerequisite such as needing a live instance/hardware registration. Usage is only implied by the word 'reset'.

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