Skip to main content
Glama

gc_controller_press_once

Send a single GameCube button press by pressing, holding for a configurable duration, and releasing automatically, so agents avoid pairing separate press and release calls.

Instructions

Tap a button once: press, hold for hold_duration ms, then release.

This is the recommended way to send a button press for agent use. It is a single atomic action — you do not need to pair gc_controller_press and gc_controller_release. The button is always released afterwards.

hold_duration defaults to 200 ms. Pass a larger value to hold the button longer (e.g. to hold START through a loading screen).

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

Input Schema

NameRequiredDescriptionDefault
portYes
buttonYes
instance_idYes
hold_durationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most important behavioral trait: the button is always released afterwards, making the call self-contained and safe from stuck-button states. It does not cover failure behavior (what if release fails mid-hold) or whether the call blocks for the hold duration, which is the main remaining gap for a timing-sensitive action.

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?

Front-loaded with the action, then the atomicity rationale, then the optional-argument note — a sensible order with little waste. The phrase "for agent use" is slightly redundant, but the rest of the wording earns its place.

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 four-parameter action tool with no annotations and no output schema, the description covers execution semantics well but leaves three required parameters undocumented and says nothing about what the call returns or how errors surface. It is adequate to call the tool in the happy path but incomplete for correct parameter construction.

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% across four parameters, so the description must compensate, but it only explains hold_duration (default 200 ms, raise it to hold longer). The three required parameters — instance_id, port, and button — receive no meaning at all, leaving the agent to guess valid button names and port semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and mechanism: "Tap a button once: press, hold for hold_duration ms, then release." It explicitly contrasts this with the sibling press/release pair, so an agent can distinguish press_once from gc_controller_press and gc_controller_release without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternatives (gc_controller_press + gc_controller_release) and states the condition that makes this tool preferable: it is "a single atomic action — you do not need to pair" them. It also gives a concrete use case for the non-default argument (holding START through a loading screen).

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