Skip to main content
Glama

pf2e-compendium-filter-items

Read-onlyIdempotent

Search COMPENDIUM packs for items with Pathfinder 2e structured filters (pf2e worlds only): equipment, spells, feats, ancestries, classes and 20 more Item types.

CRITICAL DATA FORMATS

  • For spells, level is the spell RANK.

  • traits are ALL-OF (every trait present); traditions are ANY-OF (arcane, divine, occult, primal). Do not confuse the two.

  • category is the feat category (class, skill, general, ancestry, ...). rarity: common, uncommon, rare, unique.

  • priceGold is gp with decimals (5 sp -> 0.5), per batch for batched goods like arrows.

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+. Results carry level (null when absent), sorted by level then name.

EXAMPLES { "type": ["spell"], "level": { "min": 3, "max": 3 }, "traditions": ["arcane"] } { "type": ["consumable"], "priceGold": { "max": 5 } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSubstring of document name, case-insensitive.
typeNoPF2e item types (OR).
levelNoItem level range; spell RANK for spells.
limitNoPage size 1..200, default 50.
offsetNoSkip first N results.
rarityNoRarity (OR).
traitsNoALL-OF: every listed trait must be present. Lowercase slugs.
packIdsNoRestrict to these Item packs; omit for all.
categoryNoFeat category (OR): class, skill, general, ancestry, ...
priceGoldNoPrice range in gp (5 sp -> 0.5).
traditionsNoANY-OF: at least one shared tradition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark it as readOnly, idempotent, and non-destructive; the description adds rich behavioral details: silent exclusion of documents lacking a filtered field, limit/offset with defaults, response fields (total, hasMore), result format ({name, uuid}), sorting order, and the bridge module requirement. No contradictions with 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?

Well-structured with sections for critical data formats, semantics, and examples. The purpose is front-loaded, and every sentence earns its place—no fluff. The length is justified by the complexity of the tool.

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?

Covers all essential aspects for correct usage: filter semantics, response format, pagination, follow-up tools, and prerequisites (bridge module). Despite 11 parameters and nested objects, nothing an agent needs to call it correctly is missing, and the lack of an output schema is compensated by the explicit result description.

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 coverage is 100%, yet the description adds critical semantics beyond the schema: spells use level as rank, traits are ALL-OF vs traditions ANY-OF, category explains feat categories, priceGold explains gp conversion and per-batch pricing, and filter combination logic (AND/OR) is clarified. This is exactly the kind of value the description should provide.

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 ('COMPENDIUM packs') with an explicit scope ('pf2e worlds only') and enumerates the item types covered. It clearly differentiates from sibling tools like pf2e-compendium-filter-actors (which searches actors) and generic compendium-search by emphasizing structured PF2e filters.

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

Usage Guidelines5/5

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

Explicitly scopes usage to PF2e worlds and explains how to follow up on results ('follow up with uuid-resolve, or compendium-browse with ids to batch-load'). While it doesn't name alternative search tools directly, the scope and filter emphasis make the intended context unambiguous.

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