Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

search-compendium-spells

Search D&D 5e spells from premium book packs by level, school, damage type, or name. Filters use real compendium data, excluding SRD spells.

Instructions

D&D 5e SPELL DISCOVERY: find spells matching faceted criteria (level, school, damage type, name) across the premium book packs only — the SRD (dnd5e.*) packs are excluded and never appear in results (design.md §2.3). Backed by the system Compendium Browser, so filters check real spell data (not name heuristics). Returns minimal hits ({id,name,type,uuid,pack,packLabel,img,facets}) premium-first ranked — identify candidates here, then pull full detail with get-compendium-entry. damageType is a two-stage refine (loads candidate spells to inspect their activities).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCase-insensitive substring to narrow by spell name (e.g., "fire", "cure wounds").
limitNoMaximum results to return (default: 50, max: 200)
damageTypeNoKeep only spells that deal this damage type (e.g., "fire", "cold", "radiant"). Two-stage: candidate spells are loaded to inspect their activities, so this narrows an already facet-filtered set.
spellLevelNoFilter by spell level — exact number (0 = cantrip … 9) or a {"min","max"} range for surveys.
spellSchoolNoSpell school(s): abjuration · conjuration · divination · enchantment · evocation · illusion · necromancy · transmutation (full name or dnd5e 3-letter key; one value or an array).
Behavior4/5

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

With no annotations, the description reveals key behaviors: premium-only scope, real data checks (not heuristics), premium-first ranking, and the two-stage damageType process. It stops short of mentioning authentication or rate limits but is thorough.

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?

The description is a single paragraph but logically ordered: purpose, scope, backend, return format, usage tip, special note. It's concise yet informative, with minimal redundancy.

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?

Given 5 parameters, no annotations, and no output schema, the description covers the essential context: return fields, ranking, scope, and follow-up tool. It could list more example values but is complete enough.

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

Parameters4/5

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

Schema coverage is 100% with descriptions. The free-text adds value by explaining the two-stage refinement for damageType and the scope restriction (premium packs only) not in 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's for discovering D&D 5e spells with faceted criteria, limited to premium book packs, and explicitly excludes SRD. This distinguishes it from sibling search tools like search-compendium-creatures and search-compendium-items.

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 provides usage guidance: use this to find candidates and then get-compendium-entry for full details. It explains the two-stage refine for damageType. While not explicitly excluding alternatives, the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Txpple/fvtt-mcp-molten5e'

If you have feedback or need assistance with the MCP directory API, please join our Discord server