Skip to main content
Glama

Play a step

step

Advance the game: shoot threats by id (auto-ranged), optionally use a zap, for a number of ticks (20 ticks = 1 second). Returns what happened, a top-down radar and every threat sorted by time to impact.

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
zapNoOptional zap on the first tick (3 per game): flash kills everything, pulse kills near and stalls far, dome shields one city.
cityNoCity index for a dome zap.
ticksNoTicks to advance. Default 4.
game_idYesThe game_id returned by new_game.
targetsNoThreat or aircraft ids to shoot, in order, as fast as the gun reloads (about 7 a second). Each shot bursts where the target will be.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 real behavior: shooting is auto-ranged, zaps are limited to 3 per game and fire on the first tick, and 20 ticks equals one second. It does not cover what happens on invalid target ids, at game over, or whether state changes are irreversible.

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?

One dense sentence, front-loaded with the action and followed by the return shape. Nothing is padded, though the clause structure is compressed enough that a reader must parse it carefully.

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?

With no output schema, the description does summarize the return payload (what happened, radar, threats sorted by time to impact), which is the key missing structured information. Error and edge-case behavior for a stateful turn-advancing tool remains unstated, keeping it short of full coverage.

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 enum values, city index, tick bounds and target list are already fully documented. The description adds the tick-to-time mapping (20 ticks = 1 second), which is genuine meaning beyond the schema, but most parameter detail is redundant with the structured fields.

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?

States a specific verb and object ('Advance the game') plus the mechanics it performs (shoot by id, optional zap, advance ticks). It implicitly separates itself from get_state and new_game by making clear this is the turn-advancing action, though it never names a sibling explicitly.

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 gameplay role is implied — you call this to move the simulation forward — but there is no explicit 'use this when...' or exclusion such as 'use get_state to inspect without advancing'. The agent must infer the alternative from the description alone.

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