Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create-actor-from-compendium

Create world actors from official compendium packs, with optional stat modifications for custom variants, and direct placement into folders or scenes.

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. Pass folder (id or exact name, created if absent) to file the copies directly — no move-documents follow-up. 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"])
folderNoActor folder to file the created copies under — a folder id or exact name (created if absent), so the actor lands in its folder in ONE call instead of create + move-documents. Omit for the default "Foundry MCP Creatures" folder.
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:{override} or ac:{natural}, 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.3
    • addedInput schema / properties / folder
      Added value: +{
+  "description": "Actor folder to file the created copies under — a folder id or exact name (created if absent), so the actor lands in its folder in ONE call instead of create + move-documents. Omit for the default \"Foundry MCP Creatures\" folder.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / modifications / description
      Previous value: -"PREFAB-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."New value: +"PREFAB-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:{override} or ac:{natural}, 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."
  2. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / disposition
      Added value: +{
+  "description": "Prototype-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).",
+  "enum": [
+    "friendly",
+    "neutral",
+    "hostile",
+    "secret"
+  ],
+  "type": "string"
+}
  3. First observedv1.2.2

TDQS

A4.6/5.0
Behavior4/5

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

The description discloses key behavioral traits: it modifies only the copy, never the source entry, and can layer modifications in the same call. It also explains folder creation behavior. Since annotations are absent, the description carries the burden, and it does a good job of revealing the non-obvious aspect of modifying only the world copy.

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 detailed and comprehensive, but it is relatively long. It uses clear formatting with dashes and section headers, which aids navigation. It front-loads the core purpose and main parameters, and then provides secondary context. It earns its length due to the complexity of the tool, but a few sentences could be tightened without losing meaning.

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 the tool's complexity (9 params, nested objects, multiple modes), the description is exceptionally complete. It covers the entire workflow: search, copy, and modify. It explains the difference between creating actors and placing tokens, and clarifies the disposition parameter. No output schema exists, but the description implies the result (created actors) without needing to detail return values.

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?

The schema has 100% description coverage, so the baseline is 3. The description adds value by clarifying the relationship and usage of the modifications, folder, and names parameters, especially the PREFAB-AS-BASE bridge requirement and the relationship between placement and addToScene. It explains that quantity is defaulted based on names length, which is not in the 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's purpose: copying actors from premium-book compendium packs. It explains the process of finding the entry, passing the packId, itemId, and names, and highlights that it is the default preferred path for official content. It also distinguishes itself from author-npc for hand-authored NPCs.

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: for premium-book compendium content, and explicitly states that it is the preferred path. It references the alternative author-npc as a last resort for fully hand-authored NPCs, and mentions the PREFAB-AS-BASE bridge for custom creatures. This gives a clear decision framework.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools