Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

send-chat-message

Post HTML messages to Foundry VTT chat with visibility options (public, GM whisper, blind, self), optionally speaking as a character and embedding images via local files or URLs.

Instructions

Post a message to the Foundry chat log as the GM bridge user. Content is HTML. Choose a visibility mode (public / gm whisper / blind / self) and optionally speak AS a character (speakerActor). Embed images via the images param (local files upload over WebDAV; Data-relative paths and https URLs link directly — uploaded files are PUBLIC). GM-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoPresentation style (defaults to ic when speakerActor is set, else ooc).
enrichNoPre-enrich content (resolve @UUID links and inline rolls) before posting.
flavorNoOptional secondary header line, e.g. "Perception Check".
imagesNoImages to embed. Local files are uploaded to the world over WebDAV and linked; Data-relative paths and https URLs are linked directly. PRIVACY: uploaded files are served publicly with no auth.
contentYesMessage body as HTML (all formatting is just HTML). Inline rolls like [[/r 1d20+5]] and @UUID[Type.id]{label} links are enriched on render. Use the images param to attach images rather than hand-writing <img>.
visibilityNopublic = everyone; gm = whisper to all GMs; blind = whisper to GMs (mainly meaningful for rolls — for plain text it behaves like gm but also sets blind); self = only the bridge user. For "public as a character", use public + speakerActor.public
imageFolderNoData-relative folder for uploaded local images (default "worlds/<world>/assets/chat").
speakerActorNoActor id / exact name / name-substring (or scene token id) to speak AS — the message renders with that character as speaker (the "public as character" mode).
overwriteImagesNoOverwrite an existing uploaded image of the same name instead of refusing.
Behavior4/5

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

No annotations provided, but description discloses key behaviors: messages posted as GM bridge user, HTML content, image uploads are public, visibility modes explained, and speakerActor capability. Good transparency for a messaging tool.

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?

Concise single paragraph, front-loads primary action. Could be more structured but effective.

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?

Complete for a message posting tool with 9 parameters. Covers main use cases, privacy warning, and GM restriction. No output schema needed.

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?

Schema description coverage is 100%, baseline 3. Description adds value beyond schema: explains public nature of uploads, 'public as a character' usage, enrich default, etc.

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?

Description clearly states the tool posts a message to Foundry chat as GM bridge user with HTML content, visibility modes, and optional speaker. Distinguishes from sibling tools like post-item-card or request-roll by focusing on general chat.

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?

Explicitly states GM-only usage and describes when to use visibility modes and speakerActor. Lacks explicit 'when not to use' but context is clear.

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