Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

manage-activity

Add, edit, remove, or list D&D 5e item activities such as attacks, damage, saves, heals, checks, utility, and spell-casting. Target actor items or world items.

Instructions

[D&D 5e only] Add / edit / remove / list Activities on an item — the rollable things (attack, damage, save, heal, check, utility, cast). Target an item on an actor (set actorIdentifier) or a world item (omit it). This authors actions like a Multiattack (action="add", type="utility", name="Multiattack"), a heal, an ability-check, a saving-throw activity, OR a spell-casting item (action="add", type="cast", spellUuid=…, charges=…, saveDC/attackBonus=… to pin a fixed challenge) — the cast LINKS a real compendium spell so its measured template + save/attack fire for free. Use action="list" (or get-actor-entity) to find activityIds, then edit/remove by id; edit takes a patch of dot-paths relative to the activity. Authoring only — it does not run combat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoActivity name (e.g. "Multiattack"). Used by add and edit (rename).
typeNoActivity type. Required for add. "utility" = descriptive action (e.g. Multiattack). "cast" = link & cast a real compendium spell (e.g. a wand/staff) — see spellUuid.
patchNoEdit: dot-paths RELATIVE to the activity root, e.g. {"attack.bonus":"3"}, {"save.dc.formula":"16"}, {"damage.onSave":"half"}.
actionYesadd a new activity, edit/remove an existing one (by activityId), or list activities.
onSaveNoSave activity: damage on a successful save.
saveDCNoSave activity: the DC. Cast activity: pins a FIXED save DC for the linked spell (else the cast defers the DC to the casting actor).
skillsNoCheck activity: associated skill keys (e.g. ["acr","ath"]).
abilityNoAttack ability override (attack activity).
chargesNoCast activity: item charges (uses) consumed per cast. Omit for an at-will cast.
checkDCNoCheck activity: the DC.
castLevelNoCast activity: level to cast at (0 = cantrip). Defaults to the spell's base level.
spellUuidNoCast activity (REQUIRED): the Compendium uuid of the spell to LINK, e.g. "Compendium.dnd-players-handbook.spells.Item.phbsplFireball00". The activity CASTS this spell — its measured template (fireball sphere, lightning line…), save/attack, and effects come for free. The spell must be a real premium-book spell (off-book/SRD is refused — if it is not in the books, STOP and ASK; do not hand-roll a fake save/damage activity).
activityIdNoActivity id — required for edit/remove. Get it from action "list" or get-actor-entity.
attackTypeNoAttack activity: melee or ranged.
healAmountNoHeal activity: healing dice (type "healing" or "temphp").
attackBonusNoAttack activity: flat to-hit bonus. Cast activity: pins a FIXED spell-attack bonus (else the cast defers the attack to the casting actor).
damagePartsNoDamage dice — for attack (extra parts), damage, and save activities.
includeBaseNoAttack: also roll the item base damage (default true).
saveAbilityNoSave activity: the saving-throw ability.
checkAbilityNoCheck activity: the ability rolled.
activationTypeNoAction economy. Default "action".
itemIdentifierYesItem to operate on (id or name). On an actor when actorIdentifier is set, else a world item.
actorIdentifierNoIf set, the item is embedded on this actor; omit to target a world (sidebar) item.
Behavior4/5

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

No annotations are present, so the description carries full behavioral disclosure. It explains that edit uses a patch of dot-paths, cast activity links a real compendium spell, and warns about requiring premium-book spells. It does not describe side effects or permissions, but the authoring nature is clear.

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 dense paragraph that efficiently conveys purpose, usage examples, and key behaviors. It is front-loaded with the main action and includes specific examples without excess. Minor structure improvements (e.g., bullet points) could aid readability, but it remains concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (23 parameters, nested objects, no output schema), the description provides a good overview but lacks explicit documentation of return values (e.g., what 'list' returns) or detailed behavior for all activity types. This gap reduces completeness for an AI agent.

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%, providing a baseline of 3. The description adds significant meaning beyond the schema by explaining overall workflow (list then edit/remove), the cast linking mechanism, and the restriction that spellUuid must be from a real premium-book spell. This enhances parameter understanding.

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 explicitly states the tool manages Activities on items (add/edit/remove/list) and lists the activity types (attack, damage, save, heal, check, utility, cast). It clearly distinguishes from sibling tools by specifying 'Authoring only — it does not run combat' and targets items on actors or world items uniquely.

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 provides clear usage context: when to use actorIdentifier vs omit for world items, how to find activityIds via 'list' or get-actor-entity, and for edit/remove by id. It excludes combat execution ('does not run combat'). It does not explicitly name alternative sibling tools, but the context is well-defined.

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