Skip to main content
Glama

Read structured Praetorium reference data

get_reference_record
Read-onlyIdempotent

Returns the structured record behind a search result, including mission cards, force dispositions (missions by opposing disposition, detachments that offer them), deployments, terrain geometry, detachments, and datasheets. Records that withhold rules text carry textSources pointing at the pinned upstream file and record id.

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": {
      "id": "<id>"
    },
    "name": "get_reference_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA reference id such as datasheet:necrons:necron-warriors: a result id from search_reference, a mission pack id from list_reference, or a referenceId from list_units or simulate_combat. Names, URLs, and unit ids are not reference 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.

Output Schema

NameRequiredDescriptionDefault
dataYes
documentYes

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. Changed1 schema field changed
    • changedOutput schema / properties / document / properties / kind / enum
      Previous value: -[
      -  "datasheet",
      -  "deployment",
      -  "detachment",
      -  "mission",
      -  "rule",
      -  "terrain"
      -]New value: +[
      +  "datasheet",
      +  "deployment",
      +  "detachment",
      +  "disposition",
      +  "mission",
      +  "rule",
      +  "terrain"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The stable id returned by search_reference or list_reference."New value: +"A reference id such as datasheet:necrons:necron-warriors: a result id from search_reference, a mission pack id from list_reference, or a referenceId from list_units or simulate_combat. Names, URLs, and unit ids are not reference ids."
  4. Changed2 schema fields changed
    • changedOutput schema / properties / document / properties / sections / items / properties / textSources / description
      Previous value: -"Where withheld rules text lives upstream; fetch it there if you need the wording."New value: +"Where withheld rules text lives upstream: the pinned file, its source, and the id of the record holding it there when the file has one. Fetch it there if you need the wording."
    • addedOutput schema / properties / document / properties / sections / items / properties / textSources / items / properties / url / format
      Added value: +"uri"
  5. Changed1 schema field changed
    • addedOutput schema / properties / document / properties / sections / items / properties / textSources
      Added value: +{
      +  "description": "Where withheld rules text lives upstream; fetch it there if you need the wording.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "source": {
      +        "enum": [
      +          "bsdata",
      +          "game-datacards"
      +        ],
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "source",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  6. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description still adds genuine behavioral detail in noting that rule-text-withholding records carry textSources pointing at the pinned upstream file and record id — an unusual payload convention an agent would otherwise miss. It says nothing about record size, error behavior for unknown ids, or variation across record types.

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?

Two sentences, front-loaded with the core action, and no filler. The second sentence is dense because of the parenthetical gloss on force dispositions, but that gloss carries real semantic information rather than padding.

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?

An output schema exists, so return values need not be spelled out, and the description nonetheless previews the payload families and the textSources convention. For a single-required-parameter read tool with complete schema coverage and rich annotations, the remaining gap (no sibling routing) is small.

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 description coverage is 100%, and the id parameter's schema text already explains accepted id origins and explicitly rules out names, URLs and unit ids. The description contributes no additional parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb ('Returns the structured record') with a clear resource and an explicit scope qualifier ('behind a search result'). It enumerates the record families covered (mission cards, dispositions, deployments, terrain, detachments, datasheets), but it never names a sibling such as get_reference, so the agent must infer the boundary from the title and id description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'behind a search result' implies the tool is a follow-up drill-down after a search, which is real if indirect guidance. There is no explicit when-not, no mention of get_reference or the list/search siblings, and no statement of prerequisites or failure modes.

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