Skip to main content
Glama

battle_bot

Look up a battle.training bot by name to get its version ratings and health, recent matches, and ladder rank.

Instructions

Bot profile: versions with ratings and health, recent matches, ladder rank. Pass a bot name from the ladder, e.g. house-starter.

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": {
      "name": "<name>"
    },
    "name": "battle_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBot name, e.g. house-starter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the shape of the response (versions, ratings, health, recent matches, ladder rank) and that it is a profile lookup, but says nothing about authentication, behavior for an unknown bot name, or how many recent matches are returned.

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 with no filler; the returned content is front-loaded and the invocation hint follows. Every clause carries information an agent can act on.

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-parameter read tool with no annotations and no output schema, the description does a fair job by listing what the profile contains. It stops short of covering error behavior, result limits, or any safety/permission context that annotations would otherwise have provided.

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% and the single parameter already carries the example 'house-starter'. The description adds meaning beyond the schema by stating that the name should come from the ladder, which disambiguates bot names from agent or version identifiers.

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 names the resource (a bot profile) and enumerates its contents: versions with ratings and health, recent matches, ladder rank. That is specific enough to distinguish it from battle_ladder (a listing) and battle_match (a single match), though it is phrased as a noun fragment rather than a verb+resource statement.

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

Usage Guidelines3/5

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

The second sentence tells the agent where a valid identifier comes from (the ladder) and gives a concrete example, which is useful invocation guidance. However, there is no explicit when-to-use/when-not statement and no sibling alternative is named, so the usage boundary is only implied.

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