Skip to main content
Glama

List compact faction units for roster planning

list_units
Read-onlyIdempotent

Returns every pickable unit in one bounded response with unit-size costs, composition, attachment relationships, roster limits, roles, keywords, and links. Without a detachment it also lists every detachment the faction can take, with its detachment points, Force dispositions, rule names and enhancement costs, so you can compare them before choosing. Include a detachment, including one a chapter takes from its codex, to list only the units it allows and receive its rules, enhancements, upgrades, and stratagems by name, cost, and timing without opening every unit page. Their rules text is at each record’s textSources. A unit’s points is what its smallest size costs in this battle size and detachment, including any wargear or enhancement the detachment makes it take; costs is the Munitorum Field Manual table for every size. Legends and Crucible datasheets are left out unless nonMatchedPlay is true. A large faction such as a Space Marine chapter can exceed what an assistant reads at once, so pass query to list only the units whose name or keywords contain it; a query nothing contains lists the units whose names are close to it, so a misspelt name still finds its unit. To see which units and detachments the faction’s top-four tournament lists take, call list_winning_lists rather than relying on memory.

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": {
      "faction": "<faction>"
    },
    "name": "list_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoList only units whose name or keywords contain this text, such as Terminator or Character, or else units whose names are close to it.
factionYesFaction id, URL slug, or display name from list_reference.
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.
battleSizeNoBattle size in points for size-dependent limits.
detachmentNoDetachment id, slug, or display name. Omit it to compare every detachment the faction can take.
nonMatchedPlayNoAlso list Legends and Crucible datasheets, which matched play does not allow.
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.

Output Schema

NameRequiredDescriptionDefault
queryYes
unitsYes
factionYes
revisionsYes
battleSizeYes
detachmentYes
detachmentsYes
nonMatchedPlayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / detachment / description
      Previous value: -"Detachment id, slug, or display name."New value: +"Detachment id, slug, or display name. Omit it to compare every detachment the faction can take."
    • addedOutput schema / properties / detachments
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "dispositions": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "enhancements": {
      +            "items": {
      +              "additionalProperties": false,
      +              "properties": {
      +                "name": {
      +                  "type": "string"
      +                },
      +                "points": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                }
      +              },
      +              "required": [
      +                "name",
      +                "points"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "points": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "referenceId": {
      +            "type": "string"
      +          },
      +          "rules": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "points",
      +          "dispositions",
      +          "rules",
      +          "enhancements",
      +          "referenceId"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "faction",
      -  "battleSize",
      -  "nonMatchedPlay",
      -  "query",
      -  "detachment",
      -  "units",
      -  "revisions"
      -]New value: +[
      +  "faction",
      +  "battleSize",
      +  "nonMatchedPlay",
      +  "query",
      +  "detachment",
      +  "detachments",
      +  "units",
      +  "revisions"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"List only units whose name or keywords contain this text, such as Terminator or Character."New value: +"List only units whose name or keywords contain this text, such as Terminator or Character, or else units whose names are close to it."
  4. Changed10 schema fields changed
    • addedInput schema / properties / nonMatchedPlay
      Added value: +{
      +  "default": false,
      +  "description": "Also list Legends and Crucible datasheets, which matched play does not allow.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "List only units whose name or keywords contain this text, such as Terminator or Character.",
      +  "maxLength": 160,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedOutput schema / properties / nonMatchedPlay
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / query
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / units / items / properties / costs / items / properties / copies
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / units / items / properties / costs / items / properties / detachment / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • changedOutput schema / properties / units / items / properties / costs / items / properties / faction / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • changedOutput schema / properties / units / items / properties / costs / items / properties / keyword / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • changedOutput schema / properties / units / items / properties / costs / items / required
      Previous value: -[
      -  "models",
      -  "cost",
      -  "keyword",
      -  "faction",
      -  "detachment"
      -]New value: +[
      +  "models",
      +  "cost"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "faction",
      -  "battleSize",
      -  "detachment",
      -  "units",
      -  "revisions"
      -]New value: +[
      +  "faction",
      +  "battleSize",
      +  "nonMatchedPlay",
      +  "query",
      +  "detachment",
      +  "units",
      +  "revisions"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / properties / units / items / properties / limit / anyOf
      Previous value: -[
      -  {
      -    "maximum": 9007199254740991,
      -    "minimum": -9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  6. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: bounded response, Legends/Crucible exclusion unless nonMatchedPlay, points-vs-costs semantics, and fuzzy query fallback. It does not describe pagination or response shape, but the output schema covers returns.

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?

Dense but front-loaded, leading with the core return and following with mode-specific behavior. Every sentence carries information, though the length is near the upper bound for a single description.

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?

For a 7-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: scope, mode selection, exclusions, and the sibling to use for tournament data. Nothing material is missing.

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 baseline is 3, but the description adds meaning beyond the schema: query's fuzzy near-match fallback, detachment accepting a chapter's codex detachment, and the points/costs distinction tied to battle size and detachment. This meaningfully enriches parameter interpretation.

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 ('Returns every pickable unit') and enumerates the payload (costs, composition, attachment relationships, roster limits, roles, keywords, links). It also distinguishes the detachment-included vs omitted modes and names the sibling list_winning_lists, so an agent can tell it apart 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?

Explicitly says to omit detachment to compare all detachments, to include one to filter to allowed units, to pass query for large factions, and to call list_winning_lists instead for tournament data. When-to-use and alternatives are both spelled out.

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