Skip to main content
Glama

gc_controller_set_trigger

Set an analog trigger value from 0 to 1 for the left or right GameCube controller trigger to simulate variable pressure during emulator or hardware input.

Instructions

Set an analog trigger value (0..1). trigger is 'L' or 'R'.

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>",
      "trigger": "<trigger>",
      "value": "<value>"
    },
    "name": "gc_controller_set_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
valueYes
triggerYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation via 'Set' and documents the input range, but it does not disclose permissions, whether the value persists, whether it overwrites prior trigger state, or what errors/returns to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with no wasted wording. The operation and key input constraints are front-loaded and easy to scan.

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 four-parameter hardware mutation with no annotations and no output schema, the description is too thin. It covers the trigger side and analog value but omits instance/port semantics, operational context, and behavioral guarantees needed to invoke the tool confidently.

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 the description must compensate for four required parameters. It usefully clarifies that 'trigger' is 'L' or 'R' and that 'value' is 0..1, but it says nothing about 'instance_id' or 'port', leaving half the parameters undocumented.

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?

The description states a specific verb and resource: 'Set an analog trigger value' for a controller. It also clarifies the value range '(0..1)' and valid trigger sides 'L' or 'R'. It does not distinguish this tool from sibling alternatives such as gc_controller_set_stick, so it falls 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?

The description explains what the tool does but gives no guidance on when to use it versus alternatives, when not to use it, or any prerequisites. Sibling tools like gc_controller_set_stick and gc_controller_press exist, but the description does not route the agent among them.

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