Skip to main content
Glama

scene-activate

Idempotent

Switch the active scene in Foundry VTT: all players see it (only one is active). Other actions (bridge module 8.19.0+): view shows it on the GM's canvas only; pull moves players (userIds, default all) to it without activating; preload loads its textures on every client.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sceneId": "<sceneId>"
    },
    "name": "scene-activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoDefault activate
levelIdNoview / pull / preload: a level of the scene (Foundry 14+)
sceneIdYesScene ID (from scene-list)
userIdsNopull: user IDs (from world-info); default every player

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
      +  "description": "Default activate",
      +  "enum": [
      +    "activate",
      +    "view",
      +    "pull",
      +    "preload"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / levelId
      Added value: +{
      +  "description": "view / pull / preload: a level of the scene (Foundry 14+)",
      +  "type": "string"
      +}
    • changedInput schema / properties / sceneId / description
      Previous value: -"Scene ID to activate (use scene-list to find)"New value: +"Scene ID (from scene-list)"
    • addedInput schema / properties / userIds
      Added value: +{
      +  "description": "pull: user IDs (from world-info); default every player",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety bar is partly covered. The description adds real context beyond that: at most one active scene, the effect reaching all players, and an explicit version prerequisite (bridge module 8.19.0+) for view/pull/preload. It stops short of describing failure modes or permission requirements for activation.

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?

Front-loads the primary behavior, then uses a compact parenthetical to enumerate the secondary actions, so a reader can stop after the first clause. The dense semicolon chain is efficient, though the branching conditions for levelId are only implied rather than spelled out.

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 four-parameter, no-output-schema tool with annotations present, the description covers the main effect, each alternate action, and a version prerequisite. Remaining gaps (permissions, what happens if the scene is not preloaded before activation, levelId applicability) are minor.

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%, so both the enum default ('Default activate') and the userIds default ('default every player') are already documented in the schema. The description reinforces the semantics of userIds under pull by contrasting it with activate, but adds little else beyond what the structured fields state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Switch the active scene in Foundry VTT') plus the key scope fact that all players see it and only one is active. It does not name sibling alternatives like scene-set or scene-get, so the agent must still infer which tool handles other scene operations.

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?

Gives clear in-tool routing: default activate, view for GM-canvas-only, pull to move players without activating, preload to warm textures on clients. What is missing is guidance relative to sibling tools (e.g. when to use scene-set instead), and the bridge-module 8.19.0+ prerequisite for the non-default actions is stated but not framed as a fallback condition.

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