Skip to main content
Glama

battle_rules

Returns theater-specific battle rules, including unit specs, map, tick rate, and limits for armor or sub simulations. Use it to configure or validate matches before running simulations.

Instructions

Rules table for a theater: unit specs, map, tick rate, limits.

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

Input Schema

NameRequiredDescriptionDefault
theaterNoarmor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 doesn't state that this is a read-only lookup, whether results are static or versioned, whether the table is large, or what the returned structure looks like beyond a bare list of categories. The only behavioral hint is that the data is scoped to a 'theater'.

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 short phrase, front-loaded with the resource and followed by its contents — no filler. It borders on under-specification rather than verbosity, but as written nothing is wasted.

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-parameter lookup with no output schema, the description does at least indicate the returned categories (unit specs, map, tick rate, limits), which is more than nothing. It still leaves the parameter's enum semantics and the overall purpose of the table unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single optional 'theater' parameter, and the description does not compensate: it never explains the 'armor' vs 'sub' enum values or that 'armor' is the default. The phrase 'for a theater' merely restates the parameter name without adding meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource (rules table for a theater) and enumerates what it contains: unit specs, map, tick rate, limits. However there is no verb — it never says it retrieves or returns — and it doesn't distinguish itself from siblings like battle_meta or battle_docs, which could plausibly also return config-like data.

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?

No when-to-use guidance at all: nothing says whether this is the call to make before simulating a match, which theater to pick, or when battle_meta/battle_docs would be preferable. The agent must infer the entire invocation context from the name.

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