Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

update-scene

Modify an existing Foundry VTT scene's name, background, grid, lighting, fog, weather, navigation, and linked documents for GM-only scene management.

Instructions

Update an existing Scene document — rename, swap its background image (Data-relative path), toggle navigation, set the navigation label, change dimensions/grid (size/type/distance/units)/padding, token vision, fog mode, lighting (darkness, global light), weather, a nav thumbnail, or the linked playlist/journal ("" clears a link). Also (parity with create-scene) deep-merges a full environment{}/fog{} mood object, re-points the saved camera (initial{x,y,scale}), or re-stamps document flags on an existing scene. Scene-document only: never touches placeables (walls/lights/tokens) and never activates the scene. GM-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fogNoA v12+ scene's full fog{} object (exploration, overlay, colors), carried whole (deep-merged).
nameNoNew scene name.
flagsNoDocument flags namespaced by scope — e.g. {"tom-cartos-import":{sourceModule,sourceId}} for import provenance/dedup. Deep-merged over any existing flags (re-stampable on update).
thumbNoData-relative path to a pre-rendered navigation thumbnail (e.g. an uploaded <id>-thumb.webp shipped by a map pack). Foundry may regenerate it on a later in-app edit, so treat it as a nice-to-have, not load-bearing.
widthNoScene width in pixels.
heightNoScene height in pixels.
fogModeNoFog of war: disabled | individual (classic per-player) | shared (party-wide).
initialNoThe saved initial camera view {x,y,scale} to restore on scene load (deep-merged).
journalNoJournalEntry id or exact name to attach as scene notes. "" clears it.
navNameNoNavigation label shown in the scene nav bar.
paddingNoScene padding fraction (0–0.5).
weatherNoWeather effect key (e.g. rain, snow, fog, leaves, rainStorm, blizzard). "" = none.
darknessNoDarkness/day-night level: 0 = full daylight, 1 = full night.
gridSizeNoGrid size in pixels.
gridTypeNoFoundry grid type (0 gridless, 1 square, 2+ hex).
playlistNoPlaylist id or exact name to auto-play on scene activation. "" clears it.
gridAlphaNoGrid line opacity 0–1 (e.g. 0.2 for a faint grid).
gridColorNoGrid line color as a hex string, e.g. "#000000".
gridUnitsNoDistance unit label per cell, e.g. "ft" (dnd5e default).
navigationNoWhether the scene appears in the navigation bar.
environmentNoA v12+ scene's full environment{} mood object, carried whole (darknessLevel, globalLight{...}, cycle, base, dark{hue,luminosity}…). Deep-merged, so a partial mood patch layers onto the scene; prefer this over the flat darkness/globalLight knobs when importing or re-mooding a pack scene.
globalLightNoGlobally illuminate the whole scene (turn the lights on).
tokenVisionNoRequire token line-of-sight to see the scene. Turn OFF for overland/illustration maps.
gridDistanceNoReal-world distance per grid cell (dnd5e default 5).
backgroundPathNoData-relative path to a new background/map image.
sceneIdentifierYesScene id or exact name.
Behavior5/5

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

The description thoroughly discloses behaviors: deep-merges for environment/fog objects, clearing links with empty string, re-stamping flags, and crucially states it never touches placeables or activates the scene, with 'GM-only' permission. Since no annotations exist, the description fully informs the agent of constraints and side effects.

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 relatively long but efficiently front-loads the main purpose. It uses a semicolon-separated list and clear sectioning. While every sentence adds value, some parameter details could be more terse. It's not the most concise but justifies its length given complexity.

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?

The description covers many aspects: parameter behaviors, usage constraints, and what it does not do. However, it lacks information about return values (since no output schema is provided) and does not mention possible errors or side effects beyond the constraints. For a tool with 26 parameters and nested objects, the description is mostly complete but falls short on return expectations.

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% with descriptions, but the tool description adds significant extra context beyond the schema—e.g., explaining deep-merge behavior for environment and fog objects, giving usage advice ('prefer this over the flat darkness/globalLight knobs when importing'), and providing examples for flags. This elevates the value well above the baseline of 3.

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 states it updates an existing Scene document and enumerates specific capabilities (rename, swap background, toggle navigation, etc.). It also explicitly limits scope ('Scene-document only: never touches placeables...') and distinguishes from create-scene by mentioning parity and deep-merge behaviors. This provides a specific verb+resource+scope, fulfilling the highest clarity.

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

Usage Guidelines3/5

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

The description notes 'GM-only' as a constraint but does not explicitly guide when to use this tool over alternatives like create-scene or for non-document operations. It mentions what it does not do (placeables, activation) but lacks 'when-to-use' vs 'when-not-to-use' guidance for sibling tools. The guidance is adequate but not explicit.

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