Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

update-journal

Update Foundry VTT journal entries: rename, replace page content, or add new pages. Target specific pages by ID. Game Master only.

Instructions

Generic JournalEntry update: rename the entry (name) and/or set page content. Content replaces the target page — pass pageId to target a specific page, newPageName to add a new page, or neither to update the first text page. For quest-style append updates use update-quest-journal instead. GM-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew journal entry name (rename).
pageIdNoTarget a specific page by id (get ids from list-journals).
contentNoHTML content to set on the target page (replaces existing content).
journalIdYesJournal entry id or exact name.
newPageNameNoIf set (without pageId), create a new page with this name from content.
playerVisibleNoSet the written page visibility: true = players can OBSERVE it (a handout), false = GM-only. Omit to leave it unchanged. To flip an EXISTING page without rewriting its content, use set-journal-page-visibility.
Behavior5/5

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

Discloses destructive behavior (content replaces existing), creation of new pages (newPageName), and that tool is GM-only. No annotations present, so description fully handles transparency.

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?

Concise, four sentences with clear front-loading. No redundant information; every sentence adds value.

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?

Covers main use cases and distinguishes from sibling, but lacks description of return value or error handling. Acceptable for a straightforward update tool.

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?

Adds meaning beyond schema by explaining interactions between pageId, newPageName, and content. Schema coverage is 100%, but description provides additional context on conditional behavior.

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 it updates a journal entry by renaming or modifying page content, and distinguishes from update-quest-journal for quest-style updates. Specific verb 'update' with resource 'JournalEntry'.

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 (generic update) and when not to (use update-quest-journal instead). Provides conditional logic for page targeting and notes GM-only restriction.

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