Skip to main content
Glama

battles_by_id_replay

Battle replay

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

Input Schema

NameRequiredDescriptionDefault
idYesThe game's own battle id (`arenaUniqueID`), as digits. A string, not a number: it runs to 19 digits.
regionYesGame server region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior1/5

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. It says nothing about what a replay contains, whether it requires authentication, how large the response is, or what the return format is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two words, which is concise but under-specified rather than efficiently concise. It fails to front-load any useful information about the tool's behavior or scope.

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

Completeness2/5

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

For a tool with required parameters and no output schema, the description is too thin to be complete. The schema covers inputs, but the description provides no context about what the replay is or how it relates to the battles_by_id endpoint.

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 description coverage is 100%: the schema clearly documents id (19-digit arenaUniqueID string) and region (enum). The description adds no additional parameter meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Battle replay' is a two-word noun phrase that restates the tool's suffix rather than stating a verb and resource. It does not distinguish the tool from siblings like battles_by_id or battles_by_id_loadouts, leaving the agent to infer the exact operation.

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

Usage Guidelines2/5

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

No when-to-use guidance is provided: no mention of prerequisites, when to choose this over battles_by_id, or any alternatives. The agent receives no routing information.

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.