Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create-macro

Create a world macro hotbar button that runs JavaScript or posts chat text, and optionally pin it to a player's hotbar with ownership in the same call. GM-only.

Instructions

Create a world Macro — a hotbar button. type "script" (default) runs JavaScript as the clicking user (e.g. dnd5e.documents.macro.rollItem("Graze") rolls that item on their assigned character); type "chat" posts its text to chat. Optionally grant a player OWNER access and pin the button to their hotbar (hotbarUser + optional hotbarSlot, default first free slot) in the same call — the way to hand a player a one-click ability. GM-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imgNoIcon path or URL for the hotbar button. Omit for Foundry's stock macro icon. A path that does not resolve on the server is replaced with the stock icon (rule 8) with a warning.
nameYesMacro name — the hotbar tooltip and its Macro Directory entry.
typeNo'script' (default) executes JavaScript; 'chat' posts its text to the chat log.script
ownerNoUser id or name granted OWNER on the macro. The hotbarUser is always granted OWNER — pass this only to grant a DIFFERENT user as well.
commandYesThe macro body. For type 'script': JavaScript run as the clicking user — e.g. dnd5e.documents.macro.rollItem("Graze") rolls the item named Graze on that user's assigned character. For type 'chat': text posted to chat verbatim (inline rolls like [[/roll 1d6]] work).
hotbarSlotNoHotbar slot 1–50 (page 1 = slots 1–10). Default: the first free slot. An occupied slot is replaced with a warning.
hotbarUserNoUser id or name whose hotbar gets the button (also granted OWNER so it's theirs to see and edit). Omit to create the macro without pinning it anywhere.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.3

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does it well: scripts run as the clicking user, chat macros post text, owner/hotbar permissions are granted, and the call is GM-only. The only behavioral detail left to the schema rather than the description is the occupied-hotbar-slot replacement warning.

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?

Dense but efficient: it front-loads the core purpose, packs the type behavior and example into one sentence, then covers optional ownership and hotbar pinning. The GM-only constraint closes it with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter creation tool with no output schema, the description covers required inputs, defaults, side effects, permissions, and a realistic example. It does not spell out every schema edge case, such as invalid image replacement, but those are in the schema and the high-level flow is fully actionable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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

Schema coverage is 100%, and the schema already explains the owner/hotbarUser relationship, command behavior, defaults, and image fallback. The description gives a helpful overview and an example but adds little parameter-level information beyond what the schema provides, so baseline 3 is appropriate.

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?

Opens with a specific action and resource: 'Create a world Macro — a hotbar button.' It immediately distinguishes the two macro types and explains what they do, and it sits cleanly apart from siblings like list-macros and delete-macro by focusing on creation plus optional hotbar pinning.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the intended use ('the way to hand a player a one-click ability') and adds the hard constraint 'GM-only.' It does not explicitly mention alternative tools for inspecting or deleting macros, but the creation context and permission boundary are clear enough.

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