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

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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026
- addedOutput schema / properties / results / items / properties / excerpt / maxLength
```
Added value: +322
```
- addedOutput schema / properties / results / items / properties / section / properties / textSources / description
```
Added 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 / results / items / properties / section / properties / textSources / items / properties / url / format
```
Added value: +"uri"
```
- addedOutput schema / properties / results / maxItems
```
Added value: +25
```

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.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is free to add real behavioral context, which it does: bounded excerpts, canonical URLs, source revisions, attribution, and the important limitation that rules text itself is not returned and records point upstream. It stops short of describing pagination or result-ordering behavior.

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, front-loaded with what is searched, followed by what comes back and the key limitation. No filler or redundant restatement of the title.

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 needn't be spelled out, and the description still usefully characterizes the payload and its upstream pointers. The main omission is pagination and the scoping parameters (pack, faction, document, cursor), which leaves the agent guessing how to narrow or page large result sets.

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 only 14%, so the description must carry more weight. It does add meaning for 'query' (name, rule number, ability, weapon, keyword) and implies the 'kinds' filter by naming datasheets, missions, rules, and detachments, but says nothing about pack, faction, document, limit, or cursor — a third of the surface remains undocumented.

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 ('Searches Praetorium's missions, rules, detachments, and datasheets') and enumerates the lookup axes (name, number, keyword, value), so an agent knows exactly what it retrieves. It does not explicitly contrast itself with siblings like list_reference or get_reference_record, but the search framing is distinctive enough.

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 only implied: the enumerated lookup axes suggest this is the tool for query-driven discovery, and the 'rules text is not included' line hints at when to follow up elsewhere. There is no explicit when-to-use/when-not or named alternative (e.g., use list_reference to browse by kind without a query).

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?