Skip to main content
Glama

Read one Praetorium reference result

get_reference
Read-onlyIdempotent

Reads the complete bounded document returned by search_reference, with its revisions and attribution. A section that withholds rules text lists textSources: the pinned upstream file and record id to fetch if you need the wording.

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

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
idYes
urlYes
kindYes
titleYes
factionYes
sectionsYes
revisionsYes
attributionYes

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 / 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 result id returned by search_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 / 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 / sections / items / properties / textSources / items / properties / url / format
      Added value: +"uri"
  5. Changed1 schema field changed
    • addedOutput schema / 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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the document is 'bounded,' includes revisions and attribution, and sections may withhold rules text while exposing textSources with the pinned upstream file and record id. That withholding behavior is not derivable from annotations or schema and is genuinely useful.

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

Conciseness5/5

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

Two sentences, zero filler. The core purpose is front-loaded and the fallback/edge-case note follows immediately. Nothing repeats the title or annotations.

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-value structure need not be described, and the description still pre-empts the most confusing return case (withheld rules text plus textSources). What it lacks is any disambiguation against get_reference_record, which matters given the near-identical sibling name.

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%, and the id parameter's schema text already enumerates the acceptable id sources and explicitly excludes names, URLs and unit ids. The description adds no syntax or format detail for id, llm_model, or conversation_id, so the schema carries the full burden and 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?

The description opens with a specific verb+resource: it 'reads the complete bounded document returned by search_reference, with its revisions and attribution,' which tells an agent this is a single-document fetch, not a search. It ties cleanly to the search_reference sibling that produces the id, but does not distinguish itself from the similarly named get_reference_record, leaving some ambiguity.

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?

Usage is implied through the reference to search_reference as the source of the result, and the closing sentence gives a conditional next step ('if you need the wording') for sections that withhold rules text. However, there is no explicit statement of when to prefer this over get_reference_record or list_reference, so the agent must infer the boundary.

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