Skip to main content
Glama

Play a step

step

Advance the game: shift lanes, fire, optionally use a superzapper, for a number of ticks (20 ticks = 1 second). Returns what happened and the new board.

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
zapNoUse one superzapper (3 per game) on the first tick. Default false.
fireNoHold fire during this step. Default true.
moveNoLanes to shift, one lane per tick. Negative moves to lower lane numbers. Default 0.
ticksNoTicks to advance. Default 4.
game_idYesThe game_id returned by new_game.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 disclose a useful behavioral fact — that the call returns what happened plus the new board — and the tick-rate conversion, but it says nothing about mutation side effects, error behavior for invalid game_id, or whether partial state persists on failure.

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?

A single tight sentence, front-loaded with the verb and resource, that packs the action set, the timing unit, and the return value with no wasted words. Nothing could be removed without losing information.

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 five-parameter, state-mutating tool with no annotations and no output schema, the description covers the essential action semantics and explicitly summarizes the return content. It stops short of describing error conditions or edge cases, but nothing critical to correct invocation is missing.

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 100%, so the schema already documents move/fire/zap/ticks semantics and defaults in detail; baseline is 3. The description adds the '20 ticks = 1 second' timing conversion, which is genuinely useful, but the superzapper limit it mentions is already stated in the schema, so the net addition is modest.

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 uses a specific verb ('Advance the game') and enumerates the concrete effects (shift lanes, fire, superzapper, ticks), which is clearly distinct from read-only siblings like get_state or high_scores. It doesn't name a sibling explicitly, but the simulation semantics are unambiguous.

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 implied by the wording ('advance the game') but there is no explicit when-to-use vs alternatives guidance, e.g., no mention of calling this instead of repeatedly polling get_state, nor any statement about when not to call it. An agent can infer the context but must do the work itself.

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