Embers: Tabletop RPG Toolkit

Search vault items

vault_search_items

Read-onlyIdempotent

Search the item library the user has access to (stock items plus their own house items). Use this to locate an item by name, type (the catalog's own item types), or ruleset. Defaults to a compact summary shape (identification + summary + weight + cost + publisher / source); pass detail: 'full' to receive each item's full description and properties array inline.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Substring match on item name (case-insensitive). Use `^name$` for an exact match.
`skip`	No	Pagination offset; pair with `limit` to walk results.
`sort`	No	Comma-separated field list. Prefix with `-` for descending (e.g. `-updatedAt,name`).
`type`	No	Item type (substring, case-insensitive). Vault item types are ruleset-specific strings; an unfiltered search shows the types a ruleset's catalog uses.
`limit`	No	Page size; defaults to 50 when omitted. Hard cap of 200.
`stock`	No	true = official content only; false = user-authored only; omit to include both.
`detail`	No	Response shape. 'summary' (default) returns identification + summary fields; 'full' returns the complete document shape (every field inline) that non-MCP clients receive by default.	summary
`ruleset`	No	Ruleset code, from list_rulesets.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

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 / description

Previous value: -"Item type (substring, case-insensitive). Vault item types are ruleset-specific strings. Common 5e / 5e24 examples: 'Weapon', 'Armor', 'Tool', 'Adventuring Gear', 'Wondrous Item'."New value: +"Item type (substring, case-insensitive). Vault item types are ruleset-specific strings; an unfiltered search shows the types a ruleset's catalog uses."

First observedSep 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the safe read-only, idempotent profile, so the description's contribution is the response-shape behavior: default to a compact summary and the requirement to pass detail:'full' for inline properties. That is genuine behavioral context beyond 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.

Conciseness4/5

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

Two sentences, front-loaded with scope and purpose before the response-shape detail. The second sentence is dense but every clause carries meaning; no filler.

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 an eight-parameter search tool with an output schema present, the description covers purpose, scope, and response shape without needing to explain return values. Pagination behavior is left to the schema's skip/limit descriptions, which is acceptable.

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 100%, so every parameter is already documented. The description restates name/type/ruleset filtering and the detail default, adding only the nuance that item types are catalog/ruleset-specific — helpful but largely redundant with the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (item library) and scopes it precisely: stock items plus the user's own house items. This distinguishes it cleanly from the many sibling search tools (vault_search_spells, vault_search_rules, vault_search_characters, vault_search_monsters).

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?

Explicitly says when to use it — 'locate an item by name, type, or ruleset' — giving the agent concrete selection criteria among filter dimensions. It does not, however, name the sibling search tools or state exclusions, so an agent must infer the item-vs-spell/rule boundary from the resource name.

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

All Embers: Tabletop RPG Toolkit 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?