Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

create-actor-from-compendium

Copy one or more actors from a premium compendium pack using packId and itemId. Apply custom names and optional stat modifications to create custom creatures without altering the source.

Instructions

Copy one or more actors from a premium-book compendium pack — the DEFAULT, preferred path for official content (e.g. pull the Owlbear from the Monster Manual). Find the entry with search-compendium / get-compendium-entry, then pass its packId + itemId plus names[] for the new actors. PREFAB-AS-BASE (the §6 step-2 bridge): to make a CUSTOM creature, copy the closest Monster Manual match and pass modifications (update-actor-shaped stat edits — cr/hp/ac/abilities/skills/defenses/biography/currency) to layer onto the world copy in the SAME call; the edits land on the copy only, never the source entry. For a fully hand-authored NPC with no compendium base, use author-npc (last resort).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namesYesCustom names for the created actors (e.g., ["Flameheart", "Sneak", "Peek"])
itemIdYesID of the specific creature entry within the pack (get this from search-compendium results)
packIdYesID of the premium-book pack containing the creature (e.g., "dnd-monster-manual.actors"). Premium MM/PHB/DMG only — never the dnd5e.* SRD (design.md §2.3).
quantityNoNumber of actors to create (default: based on names array length)
placementNoToken placement options (only used when addToScene is true)
addToSceneNoWhether to add created actors to the current scene as tokens
modificationsNoPREFAB-AS-BASE bridge: stat edits to layer onto the instantiated WORLD COPY — copy a close-matching Monster Manual creature, then customize it in one call (the §6 step-2 path). Same shape as update-actor, e.g. {cr, hp:{value,max,formula}, ac:{calc,flat}, abilities:{str,…}, skills:[{skill,proficiency}], damageResistances:{values}, biography, currency:{mode,gp,…}}. Applied to the copy ONLY — the source compendium entry is never modified. Use names[] for the name, not this. Applies to every copy when quantity > 1.
Behavior4/5

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

With no annotations, the description carries full burden. It states modifications affect only the world copy, never the source, and applies to all copies when quantity > 1. However, it does not mention potential side effects like permission requirements or limits on modifications.

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?

Dense but well-structured; front-loaded with core purpose, then specific paths. Bold key terms help readability. A few minor redundancies (e.g., mentioning author-npc twice) could be trimmed.

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, nested objects, and no output schema, the description covers all aspects: sourcing, modifications, placement, quantity relationships, and ties to sibling tools. Complete 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.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds critical context: packId restriction to premium books only (never SRD), itemId explained as from search-compendium results, modifications shape detailed with examples, placement options contextualized. Significant value 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 it copies actors from premium-book compendium packs, specifies it as the default path for official content, and distinguishes it from alternatives like author-npc (last resort).

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?

Explicitly tells when to use (preferred for official content) and when not (use author-npc for hand-authored NPCs). Provides a clear workflow: find with search-compendium, then pass IDs. Also covers the modifications path for custom creatures.

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