Skip to main content
Glama

Grade a roster

grade_roster
Read-onlyIdempotent

Grades which jobs a roster can do on the table, as the roster builder's grades do: score 0 to 100 and grade A to D overall and per category (board control, mobility, damage against reference targets, durability), placed among tournament lists of the same battle size and centred on comparedWith's armies, so a list's distance from its army's typical list reads on every army's spread. A typical tournament list scores about 70. It measures coverage, not strength: in tournament games the players' skill decided far more than any list measure, the overall grade went with winning only slightly, and more units with an even spread of points went with winning most. So never call a list competitive from its grade, and never present it as a win rate. missing names the reference targets nothing in the list can take half of alone. units gives each unit the jobs it is credited with; a leader or support character counts inside the unit it joins, so its buffs never show as its own job, and cutting it for another unit always raises board presence. A unit with one joined to it lists it under attached, with each target whose share of wounds the unit takes changes without it: with and without, where 1 is one whole target. Weigh that before cutting it. tournament, when the army has enough top-four lists, gives stapleShare (the share of its points in datasheets at least 3 in 10 of those lists field, which went with winning slightly), the staples it leaves out and its unproven datasheets that no winning list fields. calibration.lists is 'drawn' when the battle size was compared with lists drawn from 2,000-point tournament lists rather than real lists of its size, a rougher comparison, and there nothing shows that more units or an even spread go with winning. It measures units at full strength with passive rules only, from the exact simulator, so it rarely tells detachments apart; compare detachments with simulate_combat. Each row's notCalculated names units or rules it could not measure. Takes a few seconds; check the list with check_roster first, since a list that cannot be fielded still grades.

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": "grade_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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still adds real behavioral context beyond that: it measures coverage rather than strength, measures units at full strength with passive rules only, rarely distinguishes detachments, takes a few seconds, and flags unmeasurable units via notCalculated. Not a 5 only because much of the length is spent restating output semantics rather than disclosing call-time behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence alone runs well over a hundred words with nested clauses, and the block on attached units, tournament staples and calibration reads as an undifferentiated wall of prose. Nearly all content is substantive, but it is not front-loaded or scannable, and an unreferenced fragment ('centred on comparedWith's armies') adds confusion.

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 full burden of explaining return fields (missing, units, attached, tournament, calibration.lists, notCalculated) and does so in detail. It is complete for a grading tool, though the structure makes the completeness hard to extract.

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% and the nested roster object documents its fields thoroughly, so most parameter meaning lives in the schema. The description adds the expects-check_roster-first expectation and the 'shape save_roster takes' framing already in the schema, but contributes little new about the three top-level parameters and never mentions llm_model or conversation_id's analytics role.

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 plus the exact output shape: 'Grades which jobs a roster can do on the table... score 0 to 100 and grade A to D overall and per category (board control, mobility, damage against reference targets, durability)'. That level of specificity separates it cleanly from siblings like simulate_combat or compare_rosters.

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?

Gives explicit when-to-use ordering ('check the list with check_roster first, since a list that cannot be fielded still grades'), names an alternative for a related question ('compare detachments with simulate_combat'), and states exclusions ('never call a list competitive from its grade, and never present it as a win rate'). This is close to exhaustive routing guidance.

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