Skip to main content
Glama

Check a roster

check_roster
Read-onlyIdempotent

Prices a roster and lists every problem that stops it being fielded, without saving it or needing an account: the same summary get_my_roster gives a saved list. summary names each unit with its points, models, wargear, enhancements, Warlord and attachments, and gives the total; problems is empty when the list is legal. unchecked names restrictions Praetorium could not evaluate, which the player must check in the source rules before playing. freeWargearLeftOut names optional wargear that costs no points and replaces nothing but is not taken; take it with get_unit_options unless the player left it out on purpose.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "roster": "<roster>"
    },
    "name": "check_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
rosterYesA complete roster in the shape save_roster takes, such as the roster get_my_roster returns or a draft built from list_units and get_unit_options ids.
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. Changed1 schema field changed
    • addedInput schema / properties / roster / properties / name / description
      Added value: +"The roster title, or empty to have one generated from the army and kept current. Send a name only when the player chooses one."
  2. Changed5 schema fields changed
    • addedInput schema / properties / roster / properties / picks / items / properties / choices / additionalProperties / anyOf
      Added value: +[
      +  {
      +    "maxLength": 64,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "const": "",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / roster / properties / picks / items / properties / choices / additionalProperties / maxLength
      Removed value: -64
    • removedInput schema / properties / roster / properties / picks / items / properties / choices / additionalProperties / minLength
      Removed value: -1
    • removedInput schema / properties / roster / properties / picks / items / properties / choices / additionalProperties / type
      Removed value: -"string"
    • changedInput schema / properties / roster / properties / picks / items / properties / choices / description
      Previous value: -"One option per choice group, choice key to option id from get_unit_options, for groups it sets with choices: wargear, an enhancement, a detachment upgrade. Omitted groups keep their default."New value: +"One option per choice group, choice key to option id from get_unit_options, for groups it sets with choices: wargear, an enhancement, a detachment upgrade. Omitted groups keep their default; '' leaves an optional group empty."
  3. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / roster / properties / disposition / description
      Previous value: -"Force disposition id from get_unit_options' roster.dispositions; null when the detachment allows only one."New value: +"Force disposition id from get_unit_options' roster.dispositions, or null to leave the choice to each battle."
  5. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for the extra context it adds: no account needed, nothing persisted, and what each returned field means. It does not say how malformed input is handled (error vs. reported as a problem), which is the remaining gap.

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?

The core purpose is front-loaded in the first clause and every subsequent sentence adds information about the return fields. It is dense as a single block and could be split into sentences or bullets for scanability, but nothing is wasted.

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 no output schema, the description carries the return-shape burden and does so well, naming summary, problems, unchecked and freeWargearLeftOut. For a deeply nested input it covers what an agent needs, though failure behavior on invalid input remains unspecified.

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 coverage is 100% and the nested roster object is heavily documented in the schema itself, so the baseline applies. The description adds no detail about the roster payload beyond pointing at get_unit_options for wargear, leaving the schema to do all the work.

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: prices a roster and lists problems preventing it from being fielded, explicitly without saving or requiring an account. That directly distinguishes it from save_roster and from get_my_roster, the sibling whose output shape it mirrors.

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?

Clearly frames the read-only dry-run use case ('without saving it or needing an account') and routes the agent to get_unit_options for the free-wargear case. It stops short of an explicit 'call this before save_roster' rule, but the when-to-use context is unambiguous.

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