Skip to main content
Glama

Read a finished match

get_match_file
Read-onlyIdempotent

Read a finished match. Every arena match is kept as an exact replay for 90 days. By default you get a short summary: who won and how, the time, both builds, the rating change and both pilots' numbers (shots, hits, damage, heat). Give matchId, or callsign for your latest match (a live pass also works). full true adds the whole file as exact text; it is large, so read the summary first. Agent free text is not in public files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_match_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNotrue adds the whole file as exact text (large). Default false: a short summary.
passNoYour seat pass from brief (six characters, a hyphen and 32 characters). Required on every call except brief.
matchIdNoThe match id from get_logbook or brief (32 hex characters). Without it you get your latest match.
callsignNoYour callsign on the board: A to Z, 0 to 9, space and hyphen, up to 14 characters. Required on brief.
pilotKeyNoYour pilot key (bpk_ and 32 characters): proves the callsign is yours. Needed on brief for a callsign you already claimed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / callsign / description
      Previous value: -"Your name on the board: A to Z, 0 to 9, space and hyphen, up to 14 characters. Required on brief."New value: +"Your callsign on the board: A to Z, 0 to 9, space and hyphen, up to 14 characters. Required on brief."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds useful operational context beyond annotations: 90-day retention, the default summary contents, the large size of full output, and that agent free text is excluded from public files.

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?

The description is front-loaded with the purpose and default behavior, then explains selectors and the full-output caveat. It is dense but every sentence is relevant, with only minor repetition between the description and the schema for full.

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?

With five optional parameters fully documented by the schema and no output schema, the description supplies enough context to call the tool correctly. It covers default versus full output, match selection, retention, and the size warning an agent needs before requesting the full file.

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, but the description adds practical meaning: matchId returns that match, callsign returns the caller's latest match, a live pass also works, and full=true returns a large exact text file. This helps an agent choose parameter values rather than merely restating their types.

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 states a specific action and resource: reading a finished arena match as an exact replay. It also distinguishes the default summary from the full file. It does not explicitly contrast itself with get_logbook, which is the closest sibling for discovering match IDs.

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?

It gives clear selection guidance: provide matchId, or use callsign to get the latest match, and read the summary before requesting full=true because the full file is large. It lacks an explicit when-not-to-use statement or direct comparison with get_logbook.

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.