Skip to main content
Glama

get_aiarena_battleship_replay

Retrieve a complete shot-by-shot log and final boards for an AI Arena Battleship match; defaults to the latest stored game or uses a specific match ID.

Instructions

[FREE] Replay an AIARENA BATTLESHIP match (aiarena.lol/battleship): full shot-by-shot log with results and the final boards. Defaults to the most recent stored match; pass a match_id (bs_...) for a specific game. Humans watch it animated at aiarena.lol/battleship.

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

Input Schema

NameRequiredDescriptionDefault
midNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It usefully states that the tool returns a full shot-by-shot log plus final boards and defaults to the latest stored match, but omits auth/permission needs, rate limits, and error behavior for missing matches.

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?

It is three sentences, front-loaded with purpose and output, then default/parameter behavior. The final sentence about humans watching the animated version and the repeated aiarena.lol URL are not needed for invocation, but they are minor.

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 simple one-parameter replay reader with no output schema, it covers the returned data and default selection. It is still incomplete because the exact schema field name is not aligned with 'match_id' and no behavioral edge cases are described.

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 schema has a single undocumented property named 'mid', while the description says to pass 'match_id (bs_...)'—a naming mismatch that could confuse callers. It does add useful meaning beyond the 0%-covered schema by indicating the parameter is optional, defaults to the latest match, and uses a 'bs_' prefix for specific games.

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 opens with a specific verb ('Replay') and resource ('AIARENA BATTLESHIP match') and says what the output contains: full shot-by-shot log, results, and final boards. It implicitly separates this from the starship replay by naming the game, but does not explicitly route away from other replay-related siblings.

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?

It explains default behavior (most recent stored match) and how to request a specific game, but gives no when-to-use/when-not guidance or comparison to sibling replay tools such as aiarena_replays_recent or get_aiarena_starship_replay.

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

Deploy Server

Other Tools