Skip to main content
Glama

gc_controller_set_stick

Set the main or C analog stick position for a GameCube controller port by specifying X/Y values from -1 to 1, simulating directional input in Dolphin emulator or registered hardware.

Instructions

Set a stick position (analog).

stick is 'main' or 'c'. x/y are in -1..1 (0,0 = centre).

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>",
      "stick": "<stick>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "gc_controller_set_stick"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
portYes
stickYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 and largely drops it. It does not say whether the position persists until changed or reset, whether it interacts with button state, what happens if the instance is invalid, or whether concurrent calls serialize — all critical for a live controller-input mutation.

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 lines, front-loaded with the action and immediately followed by the parameter meaning and ranges. No filler, though the fragment formatting is slightly abrupt rather than explanatory.

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 five-required-parameter input mutation with no annotations and no output schema, the description covers the core stick coordinates but leaves instance targeting, port selection, and post-call state persistence unexplained. An agent could call it but might mis-handle state lifecycle.

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 description coverage is 0%, and the description compensates only partially: it explains stick values ('main' or 'c', with no statement that this is exhaustive) and the x/y range with centre semantics. The five required parameters include instance_id and port, which receive no explanation anywhere.

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 concrete verb+resource ('Set a stick position') and clarifies the analog nature, which distinguishes it from digital button tools like gc_controller_press in the sibling set. It never names a sibling explicitly, so differentiation is only implicit.

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?

Usage is only implied: the '(analog)' qualifier and the x/y range suggest this is for analog stick input rather than button presses or triggers. There is no statement of when not to use it, nor any mention of gc_controller_reset or whether a prior position must be cleared.

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