Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

manage-effect

Create, edit, delete, or list ActiveEffects that modify actor/item attributes in D&D 5e. Add changes like AC bonus or damage resistance using action verbs.

Instructions

[D&D 5e] Create / edit / delete / list ActiveEffects on an actor or an item. Effects carry changes ({key, value, type}) that modify the target — e.g. +1 AC ({key:"system.attributes.ac.bonus", value:"1", type:"add"}) or resist fire. Target the actor (actorIdentifier), an embedded item (actorIdentifier + itemIdentifier), or a world item (itemIdentifier alone). Use action="list" to find effectIds. Item effects transfer to the owning actor by default. Authoring only — it sets effect data, it does not run combat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoEffect name. Required (create); optional rename (edit).
patchNoEdit: extra dot-paths relative to the effect, e.g. {"duration.rounds": 10}.
actionYescreate a new effect, edit/delete one by effectId, or list effects.
changesNoThe effect changes. On edit this REPLACES the whole changes list.
disabledNoWhether the effect is disabled (inactive).
effectIdNoEffect id — required for edit/delete. Get it from action "list".
statusesNoStatus/condition ids this effect confers (e.g. ["prone"]).
transferNoItem effects: whether the effect transfers to the owning actor. Default true for items.
descriptionNoEffect description (HTML).
itemIdentifierNoItem to target: embedded on the actor (with actorIdentifier) or a world item (alone). Omit to target the actor itself.
actorIdentifierNoActor that owns the effects (or owns the item when itemIdentifier is also set). Also accepts a placed TOKEN id (from list-tokens) — the effect then lands on that token INSTANCE's own delta, not the base actor.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool only sets effect data and does not affect combat, and explains transfer behavior for item effects. It could additionally mention permission requirements or side effects like overwriting changes on edit.

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 that efficiently covers all key points: purpose, CRUD actions, targeting, effect structure, and limitations. It is not excessively long, but could be slightly restructured (e.g., bullet points) for easier scanning.

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 the tool's complexity (11 parameters, nested objects) and lack of output schema, the description provides sufficient context for an agent to understand CRUD operations, targeting, and the effect model. It mentions a limitation ('authoring only') but could elaborate on what happens with the created effect (e.g., no automated application).

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the effect structure (key, value, type), targeting rules (actor vs item), and that the changes list is replaced on edit. This goes beyond the schema's individual parameter 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 clearly states the tool manages ActiveEffects on actors or items with CRUD operations, providing specific examples like '+1 AC' and targeting options. It distinguishes from sibling tools like 'add-item' or 'apply-condition' by focusing solely on effects.

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?

The description explains when to use the tool for effect creation/editing/deletion/listing, and advises using action='list' to find effect IDs. It notes that the tool is for authoring only and does not run combat. However, it does not explicitly exclude alternatives like 'apply-condition' for condition management.

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