Skip to main content
Glama

gc_controller_press

Hold a specified GameCube controller button on a chosen port in a Dolphin or hardware instance; pair with a release call to complete the input.

Instructions

Press (hold) a button on a GameCube controller port.

Buttons: A, B, X, Y, Z, START, L, R, D_UP, D_DOWN, D_LEFT, D_RIGHT. Remember to call gc_controller_release (or use gc_controller_sequence).

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

Input Schema

NameRequiredDescriptionDefault
portYes
buttonYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the key stateful trait implicitly (a press persists until release, hence the release reminder), but it says nothing about failure modes, whether port must map to a live instance, or whether an unreleased button is auto-cleared on reset.

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?

Two short blocks: action first, valid values second, safety reminder last. No filler. The button enumeration earns its space given the absent enum; the trailing whitespace/newline is trivial.

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 3-required-param stateful mutation with no annotations and no output schema, the description covers the button vocabulary and the release obligation but leaves instance_id/port semantics and the return value unaddressed. Adequate to avoid misuse, not complete.

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 coverage is 0%, so the description is the only source of parameter meaning. It enumerates all valid button strings, which is genuinely useful and compensates for the missing enum, but port and instance_id remain completely unexplained (valid ranges, mapping to hardware).

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?

"Press (hold) a button on a GameCube controller port" gives a concrete verb plus resource, and the parenthetical "hold" distinguishes it from a one-shot tap. It stops short of naming gc_controller_press_once, so the agent must infer that distinction from name alone.

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?

It explicitly states the required follow-up: call gc_controller_release or use gc_controller_sequence, which is real when-to-use routing. What is missing is the inverse rule — when to prefer gc_controller_press_once for a momentary tap rather than a held press.

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