Skip to main content
Glama

Scene Management

manage_scene
Destructive

Sets active scene state, issues narrative directives, offers choices, resolves oracle questions, and skips time. Applies NPC changes and preserves countdowns during skips.

Instructions

Manage the active scene and its narrative framing — scene description, directive, choices, and oracle rolls. set overwrites the scene's description and metadata, derives the description from location only when description is omitted, and accepts fast_forward to skip an interval: changes applies NPC moves, conditions, or dispositions and skip_countdowns preserves narrative countdowns. directive replaces the active directive; choices replaces the offered options; oracle resolves a chance question and records the roll, so repeated calls are additive rather than idempotent. set and directive require the GM or Editor badge, persist to the Novel, are audited, and are undoable. Use when: setting scene state, issuing a directive, offering choices, consulting the oracle, or skipping time. Do NOT use when: recording a story beat — use manage_story (action: record); staging presence or autonomy — use manage_staging; changing the spatial model — use manage_world.

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": {
      "action": "<action>"
    },
    "name": "manage_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
beatNoStory-beat tag (set): setup, escalation, turning_point, climax, resolution, denouement.
seedNoDeterministic seed (oracle).
actionYesset, directive, presence, autonomy, choices, or oracle.
promptNoChoice prompt (choices).
choicesNoList of choices (choices).
contextNoContext for the choice (choices).
locationNoScene location (set).
questionNoQuestion to resolve (oracle).
directiveNoNarrative directive (directive).
atmosphereNoAtmosphere (set).
likelihoodNoLikelihood tier (oracle).
scene_typeNoScene-type tag or array (set).
descriptionNoScene description (set).
time_of_dayNoTime of day (set).
fast_forwardNoNarrative fast-forward (set).
allow_freeformNoAllow free-form response (choices).
adventure_sceneNoAdventure-scene waypoint anchor; empty or null clears (set).
skip_transition_hookNoSkip the scene-transition hook (set).

Output Schema

NameRequiredDescriptionDefault
textNoHuman-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
statusYesMachine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2026.10.16
    • removedInput schema / properties / after_user
      Removed value: -{
      -  "description": "Reset the pooled spoken-set for a new user turn (next_speaker).",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / confirmation
      Removed value: -{
      -  "description": "Confirmation mode (autonomy).",
      -  "enum": [
      -    "auto",
      -    "confirm",
      -    "prompt"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / creativity
      Removed value: -{
      -  "description": "Creativity (autonomy).",
      -  "enum": [
      -    "predictable",
      -    "standard",
      -    "chaotic"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / entity_ids
      Removed value: -{
      -  "description": "Entities present (presence).",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / force
      Removed value: -{
      -  "description": "NPC forced as the next speaker (cast/next_speaker).",
      -  "type": "string"
      -}
    • removedInput schema / properties / level
      Removed value: -{
      -  "description": "Autonomy level (autonomy).",
      -  "enum": [
      -    "full",
      -    "mechanical_prompt",
      -    "manual"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / mute
      Removed value: -{
      -  "description": "NPC muted from speaker selection (cast).",
      -  "type": "string"
      -}
    • removedInput schema / properties / safety
      Removed value: -{
      -  "description": "Safety tier (autonomy).",
      -  "enum": [
      -    "safe",
      -    "moderate",
      -    "hardcore"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / select
      Removed value: -{
      -  "description": "NPC selected as the manual speaker (cast/next_speaker).",
      -  "type": "string"
      -}
    • removedInput schema / properties / strategy
      Removed value: -{
      -  "description": "Speaker-selection strategy (cast).",
      -  "enum": [
      -    "manual",
      -    "natural",
      -    "list",
      -    "pooled"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / unmute
      Removed value: -{
      -  "description": "NPC restored to speaker selection (cast).",
      -  "type": "string"
      -}
  2. Changed2 schema fields changedv2026.10.15
    • removedInput schema / properties / adventure_scene / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / adventure_scene / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed6 schema fields changedv2026.10.13
    • addedInput schema / properties / after_user
      Added value: +{
      +  "description": "Reset the pooled spoken-set for a new user turn (next_speaker).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "NPC forced as the next speaker (cast/next_speaker).",
      +  "type": "string"
      +}
    • addedInput schema / properties / mute
      Added value: +{
      +  "description": "NPC muted from speaker selection (cast).",
      +  "type": "string"
      +}
    • addedInput schema / properties / select
      Added value: +{
      +  "description": "NPC selected as the manual speaker (cast/next_speaker).",
      +  "type": "string"
      +}
    • addedInput schema / properties / strategy
      Added value: +{
      +  "description": "Speaker-selection strategy (cast).",
      +  "enum": [
      +    "manual",
      +    "natural",
      +    "list",
      +    "pooled"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / unmute
      Added value: +{
      +  "description": "NPC restored to speaker selection (cast).",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "set",
      -  "directive",
      -  "presence",
      -  "autonomy",
      -  "choices",
      -  "oracle"
      -]New value: +[
      +  "set",
      +  "directive",
      +  "choices",
      +  "oracle"
      +]
  5. Changed1 schema field changedv1.0.4
    • changedInput schema / properties / beat / description
      Previous value: -"Story-beat tag (set)."New value: +"Story-beat tag (set): setup, escalation, turning_point, climax, resolution, denouement."
  6. Addedv1.0.3

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations, the description discloses that set overwrites scene description and metadata, directive replaces the active directive, choices replaces offered options, and oracle calls are additive rather than idempotent. It also states badge requirements, Novel persistence, auditing, and undoability for set and directive.

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 dense but front-loaded, starting with the tool's overall purpose before action-specific behavior and usage guidance. It is appropriately sized for a multi-action tool with 18 parameters, though some sentences are long and could be split for readability.

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?

Given the tool's complexity, the description covers action semantics, destructive overwrite behavior, permissions, persistence, auditability, idempotency, and sibling alternatives. An output schema exists, so return-value explanation is not required.

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%, so the schema already defines most parameter meanings. The description still adds useful behavioral semantics: description is derived from location only when omitted, fast_forward applies NPC changes and can skip countdowns, and oracle records the roll.

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 states a specific verb and resource: managing the active scene and its narrative framing. It enumerates the concrete operations (set, directive, choices, oracle) and explicitly distinguishes the tool from siblings such as manage_story, manage_staging, and manage_world.

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 provides explicit 'Use when' guidance covering scene state, directives, choices, oracle consultation, and time skips. It also provides a clear 'Do NOT use when' section naming alternate tools for story beats, staging, and spatial changes.

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