Skip to main content
Glama

Vector Alienspace

Play a step

step

Advance the game: slide toward an x position and hold fire for a number of ticks (20 ticks = 1 second). Returns what happened, a sky view and every alien, shot, UFO and loot pod.

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
fireNoHold fire during this step. Default true.
ticksNoTicks to advance. Default 4.
game_idYesThe game_id returned by new_game.
move_toNox position to slide toward at full speed (26 per second). Leave out to stay where you are.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the simulation side effects in the return list (aliens, shots, UFO, loot pod) and the tick-to-second conversion, which tells the agent this is a world-mutating call, but it never states whether the step can end the game, consume a life, or affect the submit_score flow.

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?

Two sentences, no filler, with the action front-loaded ahead of the return payload. "Returns what happened" is slightly vague padding before the more concrete enumeration that follows.

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 4-parameter tool with full schema coverage and no output schema, the description supplies the units, the return payload, and the effect of omitting move_to, which is most of what is needed. It stops short of covering terminal conditions (game over, scoring) that an agent looping on this tool would want.

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 genuinely adds one thing the schema lacks: 20 ticks = 1 second, which lets the agent size the ticks value in real time. It does not restate defaults or ranges, which the schema already handles well.

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?

"Advance the game: slide toward an x position and hold fire for a number of ticks" is a specific verb plus resource plus the two mechanisms of the action. It is unambiguously the simulation-advance tool rather than a read tool like get_state or a setup tool like new_game, even though no sibling is named.

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 domain — you call this to move time forward — and the omission of move_to is explained ("Leave out to stay where you are"), which is a useful when-not cue for one parameter. However, there is no statement of when to prefer this over get_state, or that new_game must precede it.

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