Skip to main content
Glama

actor-filter

Read-onlyIdempotent

Search WORLD actors with D&D 5e structured filters (dnd5e worlds only). Returns paginated {id, name} entries; call actor-get for full stats. Filters combine with AND, values inside one array with OR. Use for "undead with CR 1-5", "PCs in the party", "dragons with AC 18+", "NPCs in folder Chapter 7". For every actor unfiltered use actor-list; compendiums are NOT searched (use dnd5e-compendium-filter-actors).

CRITICAL DATA FORMATS

  • CR is a NUMBER from the exact set 0, 0.125, 0.25, 0.5, 1..30 ("1/4" -> 0.25; 0.7 is rejected).

  • Sizes are SHORT codes: tiny, sm, med, lg, huge, grg ("small" is rejected).

  • creatureType: the 14 lowercase SRD types only; subtypes ("demon") are rejected, use the base type ("fiend").

  • Ranges are {min?, max?}, inclusive; min = max for an exact match. Actors lacking a filtered field are silently excluded (PCs have no CR, vehicles no abilities, root-level actors no folder).

  • Pagination: limit 1..200 (default 50), offset; the response has total and hasMore.

EXAMPLES { "cr": { "min": 0.25, "max": 0.25 }, "type": ["npc"] } { "creatureType": ["undead"], "folder": { "name": "Chapter 3", "recursive": true } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
acNoArmor Class range.
crNoChallenge Rating range (numbers from the valid CR set). NPCs only.
nameNoSubstring of actor name, case-insensitive.
sizeNoSize short codes (OR).
typeNoActor types (OR).
levelNoCharacter level range. PCs only.
limitNoPage size, default 50, max 200.
maxHpNoMax HP range.
folderNoFolder by id or name; recursive includes subfolders.
offsetNoSkip first N results.
abilitiesNoPer-ability score ranges.
currentHpNoCurrent HP range ("find wounded actors").
dispositionNoPrototype token disposition (OR).
creatureTypeNoSRD creature types (OR), NPCs only. No subtypes: "demon" -> "fiend".
hasPlayerOwnerNotrue = actor has at least one player owner (typically PCs).

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?

Beyond the annotations (readOnlyHint=true, idempotentHint=true), the description discloses key behavioral traits: returns paginated {id, name} entries, filters combine with AND/OR, ranges are inclusive, actors lacking a filtered field are silently excluded, and pagination uses limit/offset with total/hasMore. It also details critical value constraints (CR is a number from an exact set, sizes are short codes, creatureType only SRD types) and that compendiums are not searched. This is substantial behavioral context that annotations do not provide.

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?

The description is well-structured and front-loaded: a one-sentence purpose, then usage examples, then critical data formats, then pagination details. Every sentence adds value; there is no filler or redundancy. Despite its length, it is concise relative to the complexity of 15 parameters and nested objects, and it is easy to scan due to clear section headers (CRITICAL DATA FORMATS, EXAMPLES).

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?

Given the tool's complexity (15 optional parameters, nested ranges, pagination) and the absence of an output schema, the description is remarkably complete. It explains filter combination, value constraints, edge cases (silent exclusion of actors lacking fields), pagination behavior, and directs the agent to actor-get for full stats. It also distinguishes from sibling tools. The only minor gap is behavior when no filters are provided, but the explicit note to use actor-list for unfiltered retrieval covers that context.

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?

Although the schema covers 100% of parameters with basic descriptions, the tool description adds critical semantic meaning: it explains that CR values must be from the exact set (rejecting '1/4' and '0.7'), sizes use short codes ('small' rejected), creatureType only accepts the 14 SRD base types (subtypes like 'demon' map to 'fiend'), ranges are inclusive, and missing fields are silently excluded. It also clarifies AND/OR semantics across filters. This goes far beyond the schema's per-field descriptions.

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 opens with a precise verb+resource: 'Search WORLD actors with D&D 5e structured filters (dnd5e worlds only).' It explicitly distinguishes from actor-list (unfiltered) and dnd5e-compendium-filter-actors (compendiums), so the agent knows exactly what this tool does and what it is not. The examples ('undead with CR 1-5', 'PCs in the party') further ground the purpose.

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?

The description gives explicit usage guidance: 'Use for ...' with concrete examples, and clearly states when NOT to use it: 'For every actor unfiltered use actor-list; compendiums are NOT searched (use dnd5e-compendium-filter-actors).' It names the alternative tools and the conditions that select them, leaving no ambiguity.

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