battle-training-mcp

list_matches

Retrieve recent battle matches with optional bot name filtering, including seeds, scores, and replay links.

Instructions

Recent matches, optionally filtered by bot name. Includes seeds, scores, replays.

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": "list_matches"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	No	Optional bot name filter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return payload ('seeds, scores, replays'), which is useful since there is no output schema, but it says nothing about result limits, ordering, auth requirements, or rate limits for what is presumably a public listing endpoint.

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 short sentences, zero waste, with the resource and filter condition front-loaded and the return contents following immediately.

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?

For a one-optional-param list tool this is close to adequate, and the return-field hint compensates for the absent output schema. But without annotations, key operational details (result cap, ordering by recency, pagination) are missing.

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 coverage is 100% and the single optional 'bot' parameter is already documented in the schema. The description's 'optionally filtered by bot name' merely restates that, adding no format or matching semantics (exact vs partial name).

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 resource ('recent matches') with a clear scope qualifier and the optional filter. It implicitly distinguishes itself from the singular sibling get_match, though it never names that sibling explicitly.

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?

Usage is only implied by 'recent matches, optionally filtered by bot name.' There is no statement of when to pick this over get_match, no mention of how many matches 'recent' covers, and no ordering or pagination guidance.

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

Deploy Server