Skip to main content
Glama

gc_controller_flick

Flick an analog stick to a target position, hold it briefly, then return it to center for single-action menu navigation without separate set and reset calls.

Instructions

Flick an analog stick: push to (x, y), hold, then return to centre.

This is the analog counterpart to gc_controller_press_once — a single atomic action you can use for menu navigation (e.g. nudge the stick up/down to move a cursor) without pairing set_stick/reset calls.

stick is 'main' or 'c'. x/y are in -1..1 (0,0 = centre). The stick is always returned to centre afterwards. hold_duration defaults to 200 ms.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
portYes
stickYes
instance_idYes
hold_durationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does well on the core behavior: the action is atomic, the stick is always returned to centre, and hold_duration defaults to 200 ms. It omits surrounding context an agent needs for a controller tool: whether the instance must be running/unpaused, what happens on out-of-range x/y, and whether errors are raised or swallowed.

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 one-line action summary, followed by differentiation and then parameter notes — a sensible ordering. There is minor redundancy where 'return to centre' in the first line is restated as 'always returned to centre afterwards,' but overall it is tight with no filler.

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?

No annotations, no output schema, and six parameters, so the description is the only behavioral documentation available. It adequately covers the core action and the stick/coordinate/hold semantics, but leaves instance_id and port undefined and says nothing about preconditions or failure modes. Sufficient to invoke correctly in the happy path, incomplete for edge cases.

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%, so the description must compensate, and it does for four of six parameters: stick accepts 'main' or 'c', x/y are in -1..1 with (0,0) = centre, and hold_duration defaults to 200 ms. instance_id and port are entirely undocumented in both schema and description, leaving a real gap for a 6-parameter tool.

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?

Opens with a precise verb+resource+mechanism: 'Flick an analog stick: push to (x, y), hold, then return to centre.' It explicitly names the sibling it is the analog counterpart of (gc_controller_press_once) and the manual alternative (set_stick/reset pairs), so an agent can distinguish it 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 Guidelines4/5

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

Gives a concrete use case (menu navigation, nudging a cursor up/down) and says it replaces chained set_stick/reset calls. It names the closest alternative explicitly. It stops short of stating when NOT to use it (e.g., sustained analog holding or incremental movement, where set_stick would be correct), leaving one inference to the agent.

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