Foundry MCP

dnd5e-compendium-filter-items

Read-onlyIdempotent

Search COMPENDIUM packs for items with D&D 5e structured filters (dnd5e worlds only): gear, spells, feats, class features and other Item documents. Compendium counterpart of world-item-filter.

CRITICAL DATA FORMATS

rarity is camelCase: veryRare (not "very rare"). spellSchool is the full word (evocation, not "evo").
spellLevel 0..9 (0 = cantrip) only affects type "spell"; other types are silently excluded by it.
price in GP (denominations normalized), weight in lb, decimals allowed.

SEMANTICS: filters combine with AND, values inside one array with OR. Ranges are {min?, max?}, inclusive (min = max for exact). Documents lacking a filtered field are silently excluded. limit 1..200 (default 50), offset; the response has total and hasMore. Results are {name, uuid} entries: follow up with uuid-resolve, or compendium-browse with ids to batch-load. Requires bridge module 8.11.0+.

EXAMPLES { "type": ["spell"], "spellLevel": { "min": 0, "max": 0 }, "spellSchool": ["evocation", "illusion"] } { "requiresAttunement": true, "price": { "max": 5000 }, "rarity": ["rare", "veryRare"] }

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Substring of document name, case-insensitive.
`type`	No	Item types (OR).
`limit`	No	Page size 1..200, default 50.
`price`	No	Price range in gp.
`offset`	No	Skip first N results.
`rarity`	No	Rarity (OR), camelCase: veryRare.
`weight`	No	Weight range in lb.
`packIds`	No	Restrict to these Item packs; omit for all.
`identified`	No	Filter by the identified flag.
`spellLevel`	No	Spell level 0..9 (0 = cantrip); spells only.
`isContainer`	No	Only containers.
`spellSchool`	No	Spell schools (OR), full words.
`hasActivities`	No	Only items with usable activities.
`requiresAttunement`	No	Only items that require attunement.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations include readOnlyHint and idempotentHint, which are consistent with the description. The description adds critical details like rarity casing, spellLevel semantics, price/weight formats, and the exclusion of documents lacking filtered fields. It also mentions limit/offset and the response structure. No contradiction.

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?

Well-structured with clear sections for critical data formats, semantics, and examples. A bit long but dense with essential information. The examples are particularly useful.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description explains the response format ({name, uuid} entries, total, hasMore) and provides follow-up tool suggestions. It also notes the bridge module requirement. For a complex filter tool with 14 parameters, this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description significantly adds value by explaining filter combination (AND/OR), range inclusivity, and the special note that spellLevel only affects spells. It also provides examples that clarify parameter usage beyond the bare schema.

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?

The description clearly states it searches compendium packs for items with structured filters, specifying it's the compendium counterpart of world-item-filter. It lists the types of items covered (gear, spells, feats, class features) and distinguishes it from other tools.

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?

Provides clear context on when to use (searching compendium items) and mentions the compendium counterpart relationship. Does not explicitly list alternatives or when-not-to-use, but the scope is clear enough.

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

All Foundry MCP 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?