Skip to main content
Glama

battle_match

Fetches detailed match data and per-side statistics by match ID so you can review outcomes and compare each side's performance.

Instructions

Match detail with per-side stats.

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_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMatch id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and discloses almost nothing: it does not confirm this is a non-mutating read, does not say what happens with an unknown or malformed id, and does not mention auth, rate limits, or whether historical matches are all retrievable. Only the phrase 'per-side stats' gives behavioral signal about output structure.

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?

A single short, front-loaded fragment with no wasted words. It is efficient to the point of terseness, but nothing is buried or padded.

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

Completeness3/5

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

The tool is simple (one required string, no nesting, no output schema), so a short description is defensible, and 'per-side stats' partially hints at the return shape. Still, with no annotations and no output schema, the definition leaves the agent without confirmation of read-only behavior or id format.

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 (100% coverage) as 'Match id', so the schema already does the work. The description adds no format, provenance, or accepted-value detail beyond that, which is the expected baseline of 3 for a one-parameter tool.

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?

Names a specific resource ('Match detail') and adds what the payload includes ('per-side stats'), so the agent can tell it is a single-match lookup rather than a listing tool. No sibling is named or contrasted, and the verb is implied rather than stated, which keeps it just 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 Guidelines2/5

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

There is no when-to-use guidance at all: no statement of when to pick this over battle_live, battle_replay, or any other sibling, and no preconditions such as needing a valid match id. The agent must infer selection purely from the tool name.

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