Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Search vault rules

vault_search_rules
Read-onlyIdempotent

Search the rules library the user has access to (stock content plus their own house rules). Use this to locate a rule by name, type (the type field lists the rule types), or ruleset. Defaults to a compact summary shape (identification + summary + categories + publisher / source); pass detail: 'full' to receive each rule's full description and embedded sub-document arrays inline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vault_search_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMatches the rule's name or any other name it is known by (a stock rule with a generic name also answers to its rulebook name), ignoring case, apostrophe style, spaces, and hyphens. Results show the stock name. Use `^name$` for an exact match.
skipNoPagination offset; pair with `limit` to walk results.
sortNoComma-separated field list. Prefix with `-` for descending (e.g. `-updatedAt,name`).
typeNoRule category to filter to.
limitNoPage size; defaults to 50 when omitted. Hard cap of 200.
stockNotrue = official/WOTC content only; false = user-authored house rules only; omit to include both.
detailNoResponse shape. 'summary' (default) returns identification + summary fields; 'full' returns the complete document shape (every field inline) that non-MCP clients receive by default.summary
rulesetNoRuleset code, from list_rulesets.
characterNoMongo `_id` of the vault Character you are picking content for (adding to its sheet, building or levelling it). Pass it whenever the results are offered for a particular Character: the stock records its Worlds hide are left out, as in the app's own pickers. An id that names no Character the user can see is ignored.

Output Schema

NameRequiredDescriptionDefault
resultsNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / character
      Added value: +{
      +  "description": "Mongo `_id` of the vault Character you are picking content for (adding to its sheet, building or levelling it). Pass it whenever the results are offered for a particular Character: the stock records its Worlds hide are left out, as in the app's own pickers. An id that names no Character the user can see is ignored.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Substring match on rule name (case-insensitive). Use `^name$` for an exact match."New value: +"Matches the rule's name or any other name it is known by (a stock rule with a generic name also answers to its rulebook name), ignoring case, apostrophe style, spaces, and hyphens. Results show the stock name. Use `^name$` for an exact match."
  3. Changed2 schema fields changed
    • changedInput schema / properties / ruleset / description
      Previous value: -"Ruleset code (e.g. '5th Edition', '5e24', 'PFRPG', 'Savage Worlds', 'Universal')."New value: +"Ruleset code, from list_rulesets."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "Ability",
      -  "Feat",
      -  "Action Card",
      -  "Hindrance",
      -  "Edge",
      -  "Class",
      -  "Background",
      -  "Race",
      -  "Species",
      -  "Ancestry",
      -  "Glossary",
      -  "Stunt",
      -  "Extra"
      -]New value: +[
      +  "Ability",
      +  "Feat",
      +  "Glossary",
      +  "Action Card",
      +  "Hindrance",
      +  "Edge",
      +  "Class",
      +  "Background",
      +  "Race",
      +  "Species",
      +  "Ancestry",
      +  "Stunt",
      +  "Extra"
      +]
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's main burden is response shape. It discloses the default compact summary shape and the detail: 'full' option with inline sub-document arrays, which is useful behavioral context beyond annotations. It omits pagination/sorting behavior, but the schema covers it.

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, front-loaded with scope and use case, followed by the response-shape default. No filler or redundant restatement.

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?

For a nine-parameter search tool with a full input schema, output schema, and read-only annotations, the definition supplies the scope, search dimensions, and default response shape. It does not cover every filter (e.g., character or stock), but the schema descriptions carry those details.

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?

With 100% schema description coverage, the schema already explains all nine parameters. The description reinforces that name, type, and ruleset are searchable and explains the summary/full response shape, but most of that is also present in schema descriptions. Baseline 3 is appropriate.

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 gives a specific verb ('Search') and resource ('rules library'), and scopes it to content the user can access (stock plus house rules). It does not explicitly contrast with vault_get_rule, but the search/locate framing is enough to separate it from a direct single-record getter.

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

Usage Guidelines4/5

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

It states a clear use case: locate rules by name, type, or ruleset. It does not mention when not to use it or name an alternative such as vault_get_rule, so it stops short of full routing guidance.

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