Skip to main content
Glama

Import an army list

import_roster
Read-onlyIdempotent

Reads a pasted army list into a roster draft without saving it or needing an account, as the site's import does. Takes the whole text export from the official Warhammer 40,000 app, New Recruit, BattleBase, ListForge, Warscribe, WTC layouts, Mini Headquarters or Praetorium, or a Praetorium exchange code (PR1./PR2.). draft is the list in the shape check_roster and save_roster take, or null when no faction matched. review is what the importing player sees: matchedEntries of sourceEntries, the points the text reported against currentPoints at the selected rules version, notImported (units, detachments or lines left out, each with why) and builtByDatasheet (units that imported but keep their datasheet defaults for the choices named, each with why). Tell the player about every row in both before relying on the draft. When battleSizeStated is false the draft uses 2000 points; ask the player. Anything the import had to assume, such as a unit's god, is named in builtByDatasheet; nothing is substituted silently.

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": {
      "file": "<file>"
    },
    "name": "import_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesThe complete export text, or an exchange code.
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. 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. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds substantial context beyond them: no persistence, no account needed, the assumption that an unstated battle size defaults to 2000 points and must be confirmed with the player, and the guarantee that substitutions (e.g. a unit's god) are always disclosed in builtByDatasheet rather than applied silently. That is exactly the kind of behavioral caveat annotations cannot express.

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 what the tool does and does not do, then moves to the supported inputs and the review payload, which is a sensible order. It is dense and long, with a few clauses (the full source list, the restated review semantics) that could be trimmed, but nearly every sentence carries information an agent needs.

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?

There is no output schema, so the description must carry the return shape, and it does: draft (or null when no faction matched) plus review with matchedEntries, reported points vs currentPoints at the selected rules version, notImported with reasons, and builtByDatasheet with reasons. Given a single required text parameter, this leaves nothing material unexplained for correct invocation.

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, but the description goes further on the critical 'file' parameter by enumerating the accepted source families (40k app, New Recruit, BattleBase, ListForge, Warscribe, WTC layouts, Mini Headquarters, Praetorium) and the PR1./PR2. exchange-code form. llm_model and conversation_id are left entirely to the schema, which is acceptable since they are self-documented analytics fields.

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?

Names a specific verb and resource ('Reads a pasted army list into a roster draft') and immediately pins down scope with 'without saving it or needing an account'. It also disambiguates from siblings by defining draft as 'the list in the shape check_roster and save_roster take', so the agent can place it in the pipeline without opening other schemas.

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?

The description makes the position in the workflow clear: this produces a draft that check_roster and save_roster consume, and it explicitly does not save or require an account. It also tells the agent to surface every row of notImported and builtByDatasheet to the player and to ask about battle size when battleSizeStated is false. It stops short of an explicit 'use X instead when...' exclusion naming a sibling, so 4 rather than 5.

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