Praetorium

Search the Praetorium game reference

search_reference

Read-onlyIdempotent

Searches Praetorium’s missions, rules, detachments, and datasheets by name, number, keyword, and value. Returns bounded excerpts with canonical URLs, source revisions, and attribution. Rules text is not included; records point to it upstream.

Input Schema

TableJSON Schema

Name	Required	Description
`pack`	No
`kinds`	No
`limit`	No
`query`	Yes	A name, a printed rule number, an ability, a weapon, or a keyword.
`cursor`	No
`faction`	No
`document`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`results`	Yes
`revisions`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

changedInput schema / properties / query / description

Previous value: -"Words, a printed rule number, an ability, a weapon, or a rules phrase."New value: +"A name, a printed rule number, an ability, a weapon, or a keyword."

addedOutput schema / properties / results / items / properties / section / properties / textSources

Added value: +{
+  "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 cover the safety profile (readOnly, idempotent, non-destructive), so the description's value-add is the output contract: bounded excerpts, canonical URLs, source revisions, attribution, and the explicit limitation that rules text is not returned and must be followed upstream. That is real behavioral context an agent cannot get from the annotations.

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?

Three tight sentences: what it searches, what it returns, and the key limitation. Front-loaded with the verb and resource, and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-format detail is a bonus rather than a requirement, and the rules-text caveat is well placed. However, for a 7-parameter tool with near-zero schema coverage, the scoping parameters (pack, faction, document, cursor) are left undocumented in both places, leaving gaps an agent would have to guess at.

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 only 14% across 7 parameters, so the description carries most of the burden. It clarifies query semantics (name, number, keyword, value) and implicitly maps to several kinds enum values via the listed record types, but pack, faction, document, cursor, and limit are entirely unaddressed.

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 (searches) and resource set (missions, rules, detachments, datasheets) plus the matching facets (name, number, keyword, value). It doesn't explicitly contrast itself with the nearby siblings list_reference and get_reference_record, so an agent must infer that this is the query-driven variant rather than the browse-by-id variant.

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 enumeration of matchable facets implies when this tool is appropriate (free-text or printed-number lookups), but there is no explicit when-to-use/when-not or named alternative among list_reference, get_reference, and get_reference_record. Usage is inferable rather than stated.

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.