Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search-compendium-items

Locate D&D 5e equipment across premium compendium packs by name, rarity, item type, or properties. Filter results to gear, weapons, armor, or consumables; SRD content never appears.

Instructions

D&D 5e ITEM/GEAR DISCOVERY: find equipment, weapons, armor, consumables, and treasure matching faceted criteria (rarity, subtype, properties, magical, 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 item 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. Use documentType to narrow the item family (gear=all, or weapon/armor/consumable).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCase-insensitive substring to narrow by item name (e.g., "flame", "healing").
limitNoMaximum results to return (default: 50, max: 200)
rarityNoRarity/-ies: common · uncommon · rare · very rare · legendary · artifact (case- and space-insensitive; one value or an array).
magicalNoIf true, keep only items flagged magical (the "mgc" property).
itemTypeNodnd5e item SUBTYPE key (system.type.value), e.g. "wand" · "wondrous" · "rod" · "ring" · "potion" · "scroll" · "ammo"; for weapons the weapon-type key (e.g. "martialM"). One value or an array.
propertiesNoKeep items carrying ANY of these dnd5e property keys (e.g. "mgc" = magical, "fin" = finesse, "ver" = versatile).
documentTypeNoItem family to search: "gear" = everything (weapons, armor/equipment, consumables, tools, loot, containers); or narrow to "weapon", "armor", or "consumable".gear

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.3
    • removedInput schema / properties / magical / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "string"
-  }
-]
    • addedInput schema / properties / magical / type
      Added value: +[
+  "boolean",
+  "string"
+]
  2. First observedv1.2.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that it excludes SRD packs, uses real item data, returns minimal hits with a specific field list, ranks premium-first, and is for identification. This is substantial behavioral disclosure, though it doesn't cover error cases or rate limits. Given no annotations, this is strong.

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 dense but each sentence adds value: it defines the tool's purpose, scope, behavior, return format, and workflow. It's not as concise as possible but it's appropriately structured with key info front-loaded. It earns a 4.

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?

The description covers the tool's scope, exclusions, return format, ranking, and workflow, and it mentions the underlying system. Given the tool has 7 parameters but they are fully documented in the schema, and there is no output schema, the description provides sufficient context for an agent to use it correctly. It even references a design doc section. It's complete.

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 the baseline is 3. The description adds some context by summarizing the faceted criteria and mentioning the documentType usage, but it doesn't add meaning beyond the schema's own descriptions. It doesn't clarify relationships between parameters or provide examples. Thus a 3 is appropriate.

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 finds D&D 5e items matching faceted criteria, specifies the resource (premium book packs only, SRD excluded), and distinguishes itself from related tools like search-compendium-spells and get-compendium-entry by indicating it's for candidate identification. The verb 'discovery' and explicit scope make it unambiguous.

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 context for when to use: when searching for items across premium packs, and it suggests a follow-up with get-compendium-entry for full detail. It also instructs to use documentType to narrow the item family. However, it does not explicitly mention when not to use it or alternatives like search-compendium, so it's clear but not exhaustive.

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

Deploy Server

Other Tools