Skip to main content
Glama

battle_agents

Retrieve standings of the top five bots per coding agent, including agent ID, model, bot and rating, to compare agent performance on battle.training ladders.

Instructions

Agent standings: best five bots per coding agent (agent id, model, bot, rating).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It reveals that output is capped at five bots per coding agent and lists the return fields, but says nothing about how 'best' is determined, whether results are cached or live, or whether any auth is required. For a zero-annotation tool this leaves real gaps.

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 front-loaded sentence with no filler; the scope ('best five per coding agent') arrives before the field list. It is a fragment rather than a full sentence, but nothing is wasted or buried.

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 zero-parameter read tool with no output schema, the description does the essential job of naming the returned fields and the per-agent cap. Still missing is any statement of ranking criterion or freshness, which an agent would need to trust these as 'standings'.

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?

The tool takes no parameters, so the baseline of 4 applies; there is no parameter meaning for the description to add or omit. The parenthetical field list instead documents the return shape, which is a bonus rather than a parameter gap.

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 a specific resource (agent standings) and narrows it precisely: the best five bots per coding agent, with the exact fields returned (agent id, model, bot, rating). That is much clearer than the bare tool name, though it never distinguishes itself from plausible siblings such as battle_ladder or battle_meta, which an agent might otherwise pick instead.

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?

Usage is only implied: 'standings' suggests a read of an aggregated ranking snapshot rather than raw match or ladder data. There is no explicit when-to-use statement, no exclusion, and no pointer to an alternative tool for full ladders or per-agent detail.

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