Skip to main content
Glama

List public battles

list_public_battles
Read-onlyIdempotent

Lists the battles anyone may watch on Praetorium, newest first, up to 25 a page, narrowed and ordered as the battles page's public tab is. Each battle has its url, token, status, ending, size, mission and one entry per seat (side, result once finished, army, faction, detachments, score with its primary and secondary halves, rating change). A filtered page can come back short or empty while nextCursor is set; keep paging until nextCursor is null. Read one with get_public_battle.

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

Input Schema

NameRequiredDescriptionDefault
orderNooldest for oldest first; omit for newest first.
beforeNonextCursor from the previous page; omit for the first page.
filterNo
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered upstream. The description still adds genuinely non-obvious behavior: the fixed 25-per-page size, default newest-first ordering, and the counterintuitive case where a filtered page returns short or empty while nextCursor remains set. Missing is anything about rate limits or empty-result causes beyond filtering.

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?

Front-loaded with purpose, scope and ordering before the field inventory, with zero filler sentences. Sentence two's long parenthetical inventory of seat fields is the only dense stretch, and it earns its place because no output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-shape burden and does so: it enumerates the battle-level and per-seat fields a caller will receive. Combined with the pagination caveat, ordering default, page size, and the pointer to the single-record sibling, an agent has everything needed to call it correctly.

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?

Schema description coverage is 80%, so the schema already explains order, before/nextCursor, and every filter sub-object in detail. The description restates the default ordering and cursor usage but adds no syntax or constraint detail the schema lacks, and says nothing about the analytics parameters (llm_model, conversation_id). Baseline 3 applies when the schema does the heavy lifting.

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

Purpose5/5

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

Specific verb+resource (lists public battles), plus scope qualifiers: 'battles anyone may watch on Praetorium', default ordering 'newest first', and page size 'up to 25 a page'. It also separates itself from the single-record sibling by ending with 'Read one with get_public_battle.'

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

Usage Guidelines4/5

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

Gives an explicit alternative ('Read one with get_public_battle') and the condition for continued use ('keep paging until nextCursor is null'). It does not explicitly state when to prefer list_my_battles over this public list, leaving that distinction to inference from 'battles anyone may watch'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources