Skip to main content
Glama

battle_docs

Fetch official battle.training docs covering agent entry points, controller API references, Silent Service theater details, and installable agent skills.

Instructions

Fetch the official docs: llms (agent entry point), controller_api (full controller reference), controller_api_sub (Silent Service theater), skill (installable agent skill). Truncated to 12000 chars.

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

Input Schema

NameRequiredDescriptionDefault
docNollms

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 usefully discloses a hard truncation to 12000 chars, which is real value beyond structured fields, but it says nothing about what happens past the limit (continuation, offset, or unrecoverable cut), whether the call is read-only/authenticated, or what form the payload takes. The single truncation note is the only behavioral disclosure.

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 enumeration is dense but each gloss adds information. The trailing truncation note is placed last, which is slightly buried for a limit an agent needs to know before deciding how much to rely on the output.

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 lookup tool this is close, but with no output schema the description should indicate what the returned docs look like (markdown text, code blocks) and how an agent should behave when the 12000-char cap is hit. The truncation warning is present but left unresolved.

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 description coverage is 0% and the enum values carry no per-value documentation in the schema, so the description must compensate — and it does, attaching a distinct gloss to every one of the four values and flagging llms as the default entry point. Only the absence of guidance on when controller_api_sub matters over controller_api keeps it from a 5.

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 verb and resource ('Fetch the official docs') and then disambiguates each of the four doc types with a short gloss (agent entry point, full controller reference, Silent Service theater, installable agent skill). An agent can tell this is a documentation-retrieval tool distinct from the gameplay-oriented battle_* siblings, though no sibling is named explicitly.

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 'llms (agent entry point)' gloss implies an ordering — start with llms — but there is no explicit when-to-use statement, no when-not, and no guidance on switching between controller_api and controller_api_sub beyond their labels. Usage is inferable rather than stated.

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