Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

update-actor-item

Edit an embedded item on a D&D 5e actor by applying dot-path patches, deleting keys, or changing name and image. Ideal for low-level item modifications.

Instructions

[D&D 5e] Edit an item embedded on an actor (weapon / feature / spell / equipment). Apply a dot-path patch (values applied as-is; arrays/Sets replace whole) and/or deletePaths (remove keys, e.g. an activity by id), and/or change name/img. This is the low-level item editor — to add/edit/remove activities (attacks, saves, heals, etc.) prefer manage-activity, which knows the shapes. Use get-actor or get-actor-entity to find the item and the exact paths/ids to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imgNoItem image path or URL.
nameNoRename the item.
typeNoOptional item type to disambiguate the lookup (e.g. "weapon", "feat", "spell").
patchNoMap of Foundry dot-path -> value, applied as-is. Examples: {"system.damage.base.number": 3}, {"system.damage.base.types": ["fire"]} (arrays REPLACE whole), {"system.activities.<id>.attack.bonus": "2"}, {"system.equipped": true}, {"system.description.value": "<p>...</p>"}.
deletePathsNoDot-paths to delete from the item, e.g. "system.activities.<id>" to remove an activity. Converted to the Foundry "-=" deletion form for you.
itemIdentifierYesName or id of the embedded item to edit (id, exact name, then substring).
actorIdentifierYesName or id of the actor that owns the item (partial name match supported). Also accepts a placed TOKEN id (from list-tokens): the edit then lands on that token INSTANCE's own delta, not the base actor — the way to re-gear ONE placed copy of an unlinked NPC (base-actor edits never reach tokens already on a scene).
Behavior5/5

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

With no annotations, the description fully describes behavior: patch applies values as-is, arrays replace whole; deletePaths are converted to Foundry deletion form; actorIdentifier accepts token IDs for delta edits on placed tokens. This goes beyond schema details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with no wasted words. Key information is front-loaded regarding purpose and operations, and supplementary details follow logically.

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?

Given 7 parameters with only 2 required and no output schema, the description covers all essential aspects: the capabilities, how parameters work, and important nuances (e.g., token handling). It is fully sufficient for an agent to use correctly.

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?

Although schema coverage is 100%, the description adds significant meaning with concrete examples for patch and deletePaths, and explains the token instance behavior for actorIdentifier, providing practical context beyond 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 the tool edits an embedded item on an actor, detailing specific operations (patch, deletePaths, name/img). It explicitly distinguishes from the sibling manage-activity tool, making its purpose distinct.

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?

It provides explicit guidance on when to use this tool (low-level item editing) versus when to use manage-activity (activities). It also recommends using get-actor or get-actor-entity to find the item and paths, offering clear context for usage.

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