Skip to main content
Glama

scene-set

Create a scene (no sceneId; name required), copy one (cloneFrom), or change one: size, background image, grid, darkness, weather, global light, fog, token vision, initial view, linked playlist and journal. resetFog clears explored fog, regenerateThumbnail re-renders the thumbnail; level creates (name) or changes (levelId) a scene level (Foundry 14+). Paths from file-list, weather ids from scene-get weatherEffects. Removing: scene-delete; showing to players: scene-activate. Requires bridge module 8.19.0+. EXAMPLE: {"sceneId":"s1","darkness":0.8,"weather":"rain","globalLight":{"enabled":false}}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scene-set"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridNo
nameNo
levelNoScene level: {levelId?, name?, elevation: {bottom, top}, background: {src}, sort}
widthNoPixels
folderNoFolder ID (from folder-list)
heightNoPixels
paddingNo0–0.5 of the size
sceneIdNoScene ID (from scene-list); omit to create
weatherNoWeather effect id; null = none
darknessNo0 day – 1 night
resetFogNoClear explored fog for everyone
cloneFromNoScene ID to copy instead of creating empty
journalIdNoJournal opened from the scene's notes
backgroundNoBackground image path
navigationNoShow in the scene navigation bar
playlistIdNoPlaylist (from playlist-list) played on activation
globalLightNo
initialViewNoWhere the camera opens (pixels, zoom)
tokenVisionNo
darknessLockNo
journalPageIdNo
fogExplorationNo
animateDarknessNoFade to darkness over N ms
backgroundColorNo"#rrggbb"
playlistSoundIdNo
regenerateThumbnailNoRe-render the scene's thumbnail

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare the safety profile (not read-only, not destructive, not idempotent). The description adds real behavior beyond that: resetFog clears explored fog for everyone, regenerateThumbnail re-renders, the linked playlist plays on activation, and level handling requires Foundry 14+. It doesn't spell out what happens to unspecified fields on update or whether partial merges apply, which keeps it out of the top band.

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?

It is front-loaded with the three modes, then groups the field list, then closes with the escape hatches (scene-delete, scene-activate), the prerequisite, and a concrete JSON example. The telegraphic style is dense but every clause carries information.

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 high-complexity, 26-parameter, nested-object mutation tool with no output schema, the description covers the modes, ID sources, reset semantics, and version prerequisite. A handful of secondary parameters are left to the schema alone, so it is complete but not exhaustive.

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?

With 26 parameters and only 69% schema description coverage, the description compensates by naming the updateable field groups and by supplying the source of external IDs (file-list for paths, scene-get for weather, folder-list noted in the schema). It still leaves several parameters (navigation, darknessLock, animateDarkness, padding, playlistSoundId, journalPageId) undocumented in prose.

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 opens with explicit verbs and resource: 'Create a scene (no sceneId; name required), copy one (cloneFrom), or change one', then enumerates the updatable fields. It also names sibling tools (scene-delete, scene-activate) for adjacent operations, so an agent can place this tool without opening any schema.

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?

It gives the selection rule for each mode (omit sceneId to create, use cloneFrom to copy, pass levelId to change a level instead of creating one) and explicitly routes removal and player-visibility to sibling tools. It also points to file-list for paths and scene-get weatherEffects for weather ids, and states the bridge-module prerequisite.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources