Skip to main content
Glama

hold_stick

Holds an analog stick in a chosen direction for a set duration, enabling character walking, running, and camera turning in games controlled through gamepad-mcp.

Instructions

Hold an analog stick direction. stick: 'left' or 'right'. direction: up, down, left, right, or a diagonal like 'up-left'. This is how a character walks/runs and how the camera turns.

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": {
      "stick": "<stick>",
      "direction": "<direction>"
    },
    "name": "hold_stick"
  }
}

Input Schema

NameRequiredDescriptionDefault
stickYes
hold_msNo
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and leaves the important behavior unstated: whether the hold is blocking, whether it auto-releases, and how to stop a continuous hold. "Hold" implies persistence, but the agent cannot tell if the call returns immediately or after the hold completes.

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?

Three short sentences, front-loaded with the action, then the parameter vocabulary, then the gameplay context. No filler; the only slightly soft sentence is the character/camera note, which still earns its place as usage context.

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 three-parameter input tool with no annotations and no output schema, the description covers the two required parameters adequately but omits hold_ms semantics and the release/stop model. Those omissions matter for correct invocation of a continuous-hold tool.

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% and the schema declares no enums, so the description's enumeration of stick values ('left' or 'right') and direction values (cardinals plus diagonals like 'up-left') adds real meaning. However, hold_ms — a third of the parameters and the one controlling duration — is never explained, and the accepted value casing/format is only implied.

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?

"Hold an analog stick direction" gives a specific verb and resource, and the follow-up sentences explain the effect (walking/running, camera turning). It reads clearly against siblings like key_down and mouse_move, though it never names a sibling to contrast with.

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?

"This is how a character walks/runs and how the camera turns" implies when the tool applies, which is useful context. But there is no explicit guidance on when to prefer it over key_down/press, and nothing about how a hold ends (release_all is listed as a sibling but unmentioned).

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