Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

create-actor-from-compendium

Copy an official compendium actor (e.g., Monster Manual) into your world, with optional stat modifications for custom creatures.

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
dispositionNoPrototype-token disposition for the created copies — YOUR judgment call (shared authoring-policy house token rules): 'neutral' for civilians/townsfolk/bystanders, 'friendly' for allies, 'hostile' for enemies. Omit to default by source type (copied PC pregen → friendly, copied monster → hostile).
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?

In the absence of annotations, the description discloses key behaviors: edits apply only to the world copy, not the source; modifications affect all copies when quantity > 1; placement and disposition defaults are explained. However, it could mention potential rate limits or permission requirements, but covers essential mutation behavior thoroughly.

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 front-loads the core purpose. It uses bold for key terms but could benefit from bullet points or section breaks for readability. Despite length, every sentence adds necessary detail; no redundancy.

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 8 parameters with nested objects, no output schema, and multiple use cases (simple copy vs. prefab-as-base), the description fully covers both paths and references sibling tools (search-compendium, update-actor, author-npc). Provides enough context for an agent to correctly decide usage and invocation.

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%, providing baseline 3. The description adds substantial meaning: packId restricted to premium books, names shown with examples, modifications detailed with the update-actor shape, disposition with authoring policy, placement with coordinates requirement. This significantly aids parameter understanding 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 identifies the tool as copying actors from premium-book compendium packs, distinguishing it as the default path for official content and contrasting with author-npc for hand-authored NPCs. It specifies the action (copy), source (compendium), and key variant (prefab-as-base with modifications).

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 instructs to first find the entry via search-compendium/get-compendium-entry and then pass packId, itemId, and names. Provides clear alternatives: use author-npc for no compendium base, and explains the modifications parameter for the prefab-as-base bridge. Also gives disposition default rules.

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