Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

update-actor

Edit stat-block fields of existing D&D 5e actors, covering identity, details, abilities, vitals, movement, senses, defenses, resources, and currency.

Instructions

[D&D 5e only] Edit an EXISTING actor's own stat-block fields. Supply only the groups you want to change: • identity + prototype token — name, tokenName (prototype nameplate ≠ actor name), img, disposition (friend/foe), tokenAutoRotate (face movement / lockRotation), tokenRing (dynamic ring), tokenScale (art size), tokenRotation (facing) — the PROTOTYPE-token editor. (elevation / hidden / x / y are placement-only: edit those on a dropped token with update-token) • details — size, cr*, creatureType*, creatureSubtype*, swarmSize*, alignment, biography, source • abilities — abilities.{str..cha}, savingThrows (replace), skills (merge; proficiency none/proficient/expert) • vitals — hp, ac, initiative • movement, senses • defenses — damageImmunities / damageResistances / damageVulnerabilities / conditionImmunities / languages (each {mode: replace|add|remove, values, custom?}), telepathy • resources* — legendaryActions, legendaryResistances, lair • 2024* — habitat, treasure • currency — coins {mode: set|add, pp, gp, ep, sp, cp} (carried money)

Fields marked * are NPC-only (skipped with a warning on player characters). This authors the stat block; it does NOT edit embedded items (use update-actor-item / add-feature / manage-activity) or run combat. Use list-actors or get-actor to find the actorIdentifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
acNoArmor class.
crNo[NPC] Challenge rating (0.125 / 0.25 / 0.5 allowed).
hpNoHit points (value / max / temp / tempmax / formula).
imgNoPortrait image path or URL.
lairNo[NPC] Lair actions — sets the lair initiative count (marks the creature as having a lair).
nameNoRename the actor.
sizeNoCreature size (long name or short code).
sensesNoSenses ranges (feet) plus special-sense free text.
skillsNoSet skill proficiencies — merge: only the listed skills change.
sourceNoSource metadata (book / page / rules edition).
habitatNo[NPC, 2024] Habitats (replace the whole list), e.g. [{type:"forest"},{type:"planar",subtype:"nine hells"}].
currencyNoCarried coins (pp/gp/ep/sp/cp). Only the coins you list change.
movementNoMovement speeds (in the given units, default feet).
treasureNo
abilitiesNoAbility scores to set — only the abilities you list change.
alignmentNoAlignment free text (e.g. "Lawful Evil").
biographyNoBiography / description (HTML).
languagesNo
swarmSizeNo[NPC] Swarm member size, or "" if the creature is not a swarm.
telepathyNoTelepathy range (0 = none).
tokenNameNoPrototype-token nameplate, decoupled from the actor name — e.g. actor "Morgash the Gravemaker" whose dropped tokens read just "Morgash". A plain `name` rename keeps the two in lockstep; pass tokenName (alone or alongside name) to make them differ. Placed tokens keep their own name — retitle those with update-token.
tokenRingNoPrototype-token dynamic ring: false = plain token (the house default; new creations already get it), true = re-enable the ring (its colors/subject config is preserved).
initiativeNoInitiative bonus and/or ability override.
tokenScaleNoPrototype-token art scale — the "Scale (Ratio)" slider on the token Appearance tab (sets texture.scaleX and scaleY together). 1 = normal, 1.5 = 50% larger, 2 = double. Scales only the art within the token's grid footprint; it does NOT change the token's size (grid spaces).
dispositionNoPrototype-token disposition (friend vs foe). Set 'friendly' to mark an NPC an ally (e.g. a freed captive), 'hostile' for an enemy, 'neutral' for a bystander.
creatureTypeNo[NPC] Creature type: aberration, beast, celestial, construct, dragon, elemental, fey, fiend, giant, humanoid, monstrosity, ooze, plant, undead.
savingThrowsNoReplace the proficient saving throws: the listed abilities become proficient, all others non-proficient.
tokenRotationNoPrototype-token facing in degrees (0–359) — the default angle a dropped token faces. Same behavior as update-token for placed tokens: a lock-rotation prototype (tokenAutoRotate false) HIDES the angle, so setting a rotation without also setting tokenAutoRotate AUTO-UNLOCKS rotation (and warns) so the facing shows. (elevation / hidden / x / y are PLACEMENT-only — a prototype has no such fields; set those on a dropped token with update-token.)
actorIdentifierYesName or id of the actor to edit (partial name match supported). Also accepts a placed TOKEN id (from list-tokens): the edit then lands on that token INSTANCE's own actor (its delta), not the base actor — the way to edit ONE placed copy of an unlinked NPC, since base-actor edits never reach tokens already on a scene.
creatureSubtypeNo[NPC] Creature subtype free text (e.g. "Devil").
tokenAutoRotateNoPrototype-token auto-rotation: true = the token turns to face its movement (lockRotation off — the house default; new creations already get it), false = fixed facing.
damageImmunitiesNo
legendaryActionsNo[NPC] Legendary action points per round (resources.legact.max).
damageResistancesNo
conditionImmunitiesNo
legendaryResistancesNo[NPC] Legendary resistance uses per day (resources.legres.max).
damageVulnerabilitiesNo
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that fields marked with * are NPC-only (skipped with warning on PCs), explains token field behaviors (tokenName, tokenRing, tokenAutoRotate, tokenRotation), and notes that actorIdentifier can accept token IDs. However, it does not state whether the operation is safe (no destructive hint) or what the return value is.

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 long but well-structured with bullet points and clear categories. It front-loads the purpose and then organizes groups. While informative, it could be slightly more concise (e.g., some details are repeated in schema descriptions).

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?

The description covers most aspects of the tool's behavior and parameters, but it does not mention the return value (no output schema exists). Given the complexity (37 params), the description is fairly complete, but the missing output info is a notable gap.

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 84%, so the schema already documents many parameters. The description adds value by grouping parameters into logical categories (identity, details, abilities, etc.) and explaining merge/replace behavior for skills, savingThrows, defenses, and currency. It also clarifies nuances like tokenName decoupling and tokenRotation auto-unlock.

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 edits an existing actor's stat-block fields for D&D 5e, listing specific groups. It distinguishes from sibling tools like update-token, update-actor-item, and manage-activity by explicitly stating what it does NOT do.

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 provides explicit guidance on when to use this tool (to edit stat-block fields) and when to use alternatives (update-token for placement, update-actor-item for items, etc.). It also advises using list-actors or get-actor to find the actorIdentifier.

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