Skip to main content
Glama

Read a battle as a spectator

get_public_battle
Read-onlyIdempotent

Returns any battle by a token from list_public_battles or its link, as a spectator sees it on the site: battle holds its settings, round, phase, result and each player's army, score, command points and secondary cards; missions the mission each side plays; report its log as the report reads it, oldest first and 200 entries a page: each entry's seq, round, phase, the player id that recorded it (by) and a sentence saying what happened. Pass nextAfter as after for the next page. Practice battles are left out of list_public_battles but still open from their link.

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": {
      "token": "<token>"
    },
    "name": "get_public_battle"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNonextAfter from the previous page.
tokenYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them by enumerating the response shape (battle settings, round, phase, result, per-player army, score, command points, secondary cards; missions; report) and the log's ordering and page size. Pagination handling ("Pass nextAfter as after for the next page") is spelled out, which is exactly the kind of behavior annotations cannot convey.

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?

Front-loaded with the identity of the tool and dense with substance, but the semicolon-chained clauses describing battle/missions/report make it a single run-on sentence that is harder to scan than three short ones would be. Nothing is filler, though.

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

Completeness5/5

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

There is no output schema, so the description carries the full return-shape burden and does so thoroughly, including the three top-level sections (battle, missions, report), page size, ordering and continuation. Token provenance and the practice-battle exception round it out for a read-only single-resource fetch.

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?

With 75% schema coverage the schema does most of the work, but the description still adds real meaning for the two non-obvious parameters: it explains where the token originates and that the next page is fetched by passing nextAfter into after. The two analytics parameters (llm_model, conversation_id) are left entirely to the schema.

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 resource ("Returns any battle") plus the exact lookup key ("by a token from list_public_battles or its link") and the access mode ("as a spectator sees it on the site"), which separates it from the player-side get_my_battle. It stops short of naming that sibling explicitly, so an agent must infer the split from the word "spectator".

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear entry conditions: the token comes from list_public_battles or from a battle link, and it flags the edge case that practice battles never appear in the list but still open via link. No explicit when-not guidance (e.g. use get_my_battle for your own battles) is offered.

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