Skip to main content
Glama

Export a roster as text

export_roster
Read-onlyIdempotent

Writes a roster as the site's text export, the official app's layout that tournament organizers and other list builders read, without saving it or needing an account. Takes the shape save_roster takes, such as import_roster's draft or get_my_roster's roster. text is the export; code is a Praetorium exchange code that carries the exact list into Praetorium, or null when the list is too large for one. omittedUnitCount counts entries the current army data no longer prices, which the text leaves out. omittedSelectionCount counts the saved detachments and options of printed units that the current army data no longer offers, which the text also leaves out. An empty name exports the title Praetorium generates from the army. Fails while the army data is unavailable.

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": "export_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
rosterYesA complete roster in the shape save_roster takes.
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
    • changedInput schema / properties / roster / description
      Previous value: -"A complete roster in the shape save_roster takes. Its name must not be empty."New value: +"A complete roster in the shape save_roster takes."
    • 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?

Despite the readOnly annotations, the description adds real value: it clarifies that 'writes' means producing text without persisting anything, discloses the failure condition ('Fails while the army data is unavailable'), and explains the null code case and omission counts. It leaves the return shape's exact structure to be inferred, but for a non-destructive read this is strong.

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-loads the core function and the no-save clarification before the return-value detail. It is a single dense block and slightly run-on, but almost every clause (omission semantics, empty-name behavior, failure mode) carries information an agent needs given there is no output schema.

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 takes on the return-value burden and does so: text, code, omittedUnitCount and omittedSelectionCount are all explained. The nested roster input is deferred to save_roster's shape, which is reasonable given the reference, though an agent must follow that cross-reference.

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%, so the schema fully documents the roster object, llm_model and conversation_id. The description adds the roster-shape relationship and the empty-name behavior, but it mainly elaborates the return values rather than the input parameters, so it sits at the schema-backed baseline.

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 ('Writes a roster as the site's text export') and immediately distinguishes it from the save path ('without saving it or needing an account'). An agent can tell it apart from save_roster and get_my_roster 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 Guidelines4/5

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

Explains the context of use (text export in the official app's layout, no account, no saving) and names the shape it consumes by reference to save_roster, import_roster and get_my_roster. It does not explicitly state when NOT to use it (e.g., 'use save_roster instead if you want to persist'), so it stops short of full when/when-not 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