Praetorium

Read structured Praetorium reference data

get_reference_record

Read-onlyIdempotent

Returns the structured record behind a search result, including mission cards, deployments, terrain geometry, detachments, and datasheets. Records that withhold rules text carry textSources pointing at the pinned upstream file and record id.

Input Schema

Name	Required	Description	Default
`id`	Yes	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.

Output Schema

Name	Required	Description	Default
`data`	Yes
`document`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

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

Changed2 schema fields changedOct 26, 2026

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

Changed1 schema field changedOct 17, 2026

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

First observedSep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: that records withholding rules text expose textSources pointing at a pinned upstream file and record id, which tells the agent to expect partial payloads rather than missing data.

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 tight sentences with the core action front-loaded and the textSources caveat second. No filler, though the payload enumeration in sentence one is slightly list-heavy.

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 an output schema present, the description needn't detail return shapes, and it correctly focuses on what the record contains plus the withheld-rules-text behavior. The one real gap is failing to clarify its relationship to the get_reference sibling.

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 already documents its accepted sources (search_reference, list_reference, list_units, simulate_combat, datasheet: prefix) and explicitly excludes names, URLs, and unit ids. The description adds nothing further on the parameter, 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?

States a specific verb and resource ('Returns the structured record behind a search result') and enumerates the payload categories (mission cards, deployments, terrain geometry, detachments, datasheets). However, it never distinguishes itself from the sibling get_reference, which by name sounds nearly identical, leaving the agent to guess which to call.

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 caller arrives from search_reference, and the id schema hints at list_units/simulate_combat provenance. But there is no explicit when-to-use or when-not statement, and no guidance versus get_reference or list_reference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Praetorium tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?