Skip to main content
Glama

Fly a step

step

Advance the game: turn toward a target or direction, fire, thrust, and optionally raise your shield or jump to hyperspace, for a number of ticks (20 ticks = 1 second). Returns what happened, a top-down scanner and every rock, saucer, shot and loot as offsets from you.

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": {
      "game_id": "<game_id>"
    },
    "name": "step"
  }
}

Input Schema

NameRequiredDescriptionDefault
aimNoDirection [dx, dy, dz] to turn toward, used when target is left out.
fireNoHold fire during this step. Default true.
brakeNoSlow down hard. Default false.
ticksNoTicks to advance. Default 5.
shieldNoRaise the shield (uses one charge, lasts 3 seconds).
targetNoid of a rock, saucer or loot to turn toward (r12, s3, l4). Points at where it is now, with no lead.
thrustNoThrust along your nose, 0 to 1. Default 0.
game_idYesThe game_id returned by new_game.
hyperspaceNoJump to a random spot (small risk).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it states the tick/second conversion and details the return payload (what happened, top-down scanner, rocks/saucers/shots/loot as offsets). It omits consequences of the step itself — whether the state commits irreversibly, what happens on collisions or game over, and error behavior for an invalid game_id.

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?

Two sentences, front-loaded with the action and followed by the return shape. Every clause maps to actual capability; nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutating tool with no annotations and no output schema, the description supplies both action semantics and return contents, which is most of what an agent needs. It falls short on failure modes and the irreversible nature of advancing game state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning by framing aim/target/fire/thrust/shield/hyperspace as simultaneous settings applied across one batch of ticks rather than separate calls. It still leaves the shield charge economy and hyperspace risk detail to the schema.

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?

States a specific verb and effect ('Advance the game') and enumerates the composite actions (turn, fire, thrust, shield, hyperspace) with the tick budget. It is clearly distinguishable from siblings like get_state and new_game, which do not advance time.

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?

The description implies this is the main action loop, but never says when to call it versus get_state or when to prefer it over other ways of observing. No exclusions or prerequisites (beyond the game_id param) are given, so routing is inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources