Skip to main content
Glama

battle_replay

Fetch a match replay JSONL to inspect its header, tick hashes, and result, returning the first and last 20 lines for quick verification or analysis.

Instructions

Fetch a replay (.jsonl): header, tick hashes, result. Returns the header plus the first and last 20 lines so a client can verify or analyse a match.

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": {
      "id": "<id>"
    },
    "name": "battle_replay"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReplay/match id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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, and it does disclose one important behavioral trait: the response is truncated to the header plus the first and last 20 lines rather than the whole replay. It omits availability conditions (live vs completed matches), failure modes for an unknown id, and any auth or rate-limit expectations.

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 compact sentences with no filler; the identifying information (a replay, .jsonl) comes first and the return-shape detail follows. Every clause carries signal.

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?

There is no output schema, so the description must describe the return value, and it does: header, tick hashes, result, plus the 20-line truncation. For a one-parameter read tool this is close to sufficient; only truncation-related caveats (e.g., how to obtain the full replay) are left unstated.

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?

The single parameter is fully documented in the schema ("Replay/match id") at 100% coverage, so the baseline is 3. The description adds only implicit context — that the id refers to a replayable match — and gives no format or sourcing detail for the id.

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 names a specific verb and resource ("Fetch a replay"), states the format (.jsonl), and enumerates the contents (header, tick hashes, result), so an agent knows exactly what it gets back. It does not explicitly contrast itself with siblings like battle_match or battle_live, which keeps it short of a 5.

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 only implied by the closing clause "so a client can verify or analyse a match", which gives a plausible intent but no conditions such as whether the match must be finished or which cases should instead use battle_match. No explicit alternative is named.

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