Skip to main content
Glama

List public rosters

list_public_rosters
Read-onlyIdempotent

Lists the rosters players have made public on Praetorium, as the rosters page's public tab shows them, most recently saved first unless sort says otherwise. Each roster has its id, url, name, owner, faction, detachments, battle size, points under today's army data and problem, the first thing stopping it being fielded or null when it is legal. total counts every match when it is known. A page can come back short while nextCursor is set; keep paging until it is null. Read one with get_public_roster. These are players' own lists, not tournament results: for what wins, use list_winning_lists.

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

Input Schema

NameRequiredDescriptionDefault
qNoText matched against roster, owner, faction and detachment names.
sortNoupdated-desc, the default, lists the most recently saved first.updated-desc
beforeNonextCursor from the previous page; omit for the first page.
factionNoFaction id, URL slug, or display name from list_factions.
legalOnlyNoOnly rosters the current army data can field without problems.
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.
battleSizeNoOnly rosters built for this battle size in points, such as 2000.
detachmentNoWith faction, a detachment id, slug, or name from list_units, to list only rosters that took it.
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.7/5.0
Behavior5/5

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

Annotations declare read-only/idempotent/non-destructive, and the description goes well beyond that: default ordering (most recently saved first), pagination quirk ('a page can come back short while nextCursor is set; keep paging until it is null'), and the meaning of return fields including that points are evaluated under today's army data. That is substantial behavior disclosure the annotations do not carry.

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 and scope, and each sentence carries a distinct fact (ordering, return shape, paging, sibling routing, data caveat). The mid-sentence enumeration of return fields is dense and one clause ('total counts every match when it is known') is under-explained, but there is no filler.

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

Completeness4/5

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

With 9 optional parameters and no output schema, the description compensates by enumerating the returned roster fields and pagination behavior. Minor gaps remain: the analytics parameters (llm_model, conversation_id) are not contextualized and 'problem' and 'total' are only loosely defined, though the schema covers parameter-level detail.

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%, so the baseline is 3; the description adds operational meaning for the cursor parameter by explaining that short pages still require continued paging, and restates the sort default in plain terms. It adds little per-parameter beyond that, since q, faction, detachment, legalOnly and battleSize are already fully documented in the schema.

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?

States a specific verb and resource with scope ('rosters players have made public on Praetorium, as the rosters page's public tab shows them') and is explicitly differentiated from two siblings, get_public_roster and list_winning_lists, so an agent can identify it without opening a schema.

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

Usage Guidelines5/5

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

Names concrete alternatives with routing conditions: 'Read one with get_public_roster' and 'for what wins, use list_winning_lists,' plus a clarifying exclusion ('these are players' own lists, not tournament results'). The agent knows both when to pick this tool and when to pick another.

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