holonovel

Scene Management

manage_scene

Destructive

Set and manage the active TTRPG scene state, narrative directives, party presence, AI autonomy, choices, and oracle rolls, with mutations persisted to the Novel and auditable.

Instructions

Manage the active scene and its narrative framing. Mutating actions persist to the Novel and are audited; read-only actions do not mutate state. Revert the most recent mutation with manage_history (action: undo). set derives the description from location only when description is omitted. Use when: setting scene state (description, location, type), the narrative directive, party presence, AI autonomy, or when offering choices or resolving an oracle roll. Do NOT use when: recording a story beat — use manage_story (action: record).

Input Schema

TableJSON Schema

Name	Required	Description
`beat`	No	Story-beat tag (set): setup, escalation, turning_point, climax, resolution, denouement.
`seed`	No	Deterministic seed (oracle).
`level`	No	Autonomy level (autonomy).
`action`	Yes	set, directive, presence, autonomy, choices, or oracle.
`prompt`	No	Choice prompt (choices).
`safety`	No	Safety tier (autonomy).
`choices`	No	List of choices (choices).
`context`	No	Context for the choice (choices).
`location`	No	Scene location (set).
`question`	No	Question to resolve (oracle).
`directive`	No	Narrative directive (directive).
`atmosphere`	No	Atmosphere (set).
`creativity`	No	Creativity (autonomy).
`entity_ids`	No	Entities present (presence).
`likelihood`	No	Likelihood tier (oracle).
`scene_type`	No	Scene-type tag or array (set).
`description`	No	Scene description (set).
`time_of_day`	No	Time of day (set).
`confirmation`	No	Confirmation mode (autonomy).
`fast_forward`	No	Narrative fast-forward (set).
`allow_freeform`	No	Allow free-form response (choices).
`adventure_scene`	No	Adventure-scene waypoint anchor; empty or null clears (set).
`skip_transition_hook`	No	Skip the scene-transition hook (set).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	No	Human-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
`status`	Yes	Machine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.4Sep 30, 2026

changedInput schema / properties / beat / description

Previous value: -"Story-beat tag (set)."New value: +"Story-beat tag (set): setup, escalation, turning_point, climax, resolution, denouement."

Addedv1.0.3Sep 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent mutation, but the description adds real value: mutating actions persist to the Novel and are audited, read-only actions don't mutate, undo routes to manage_history, and 'set' derives description from location only when omitted. It stops short of describing auth/permission needs or what persistence means for overwritten scene fields.

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 core purpose and the persistence/audit rule before the routing clauses; four sentences with little waste. Slightly dense, but every clause earns its place.

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?

With an output schema, full parameter descriptions, and annotations present, the description only needs to supply routing and mutation semantics, which it does. Minor gap: the choices/oracle resolution actions are named but their result flow isn't described.

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% across 23 parameters with per-parameter action tags, so the schema carries the load. The description adds only two semantic nuggets (description derivation from location, undo via manage_history); baseline 3 is appropriate.

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+resource ('Manage the active scene and its narrative framing') and enumerates the six action areas (set state, directive, presence, autonomy, choices, oracle). It clearly separates itself from manage_story and manage_history, though the multi-action umbrella means the individual actions are only briefly glossed.

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?

Contains explicit 'Use when:' and 'Do NOT use when:' clauses, naming manage_story (action: record) as the alternative for story beats, plus the undo path via manage_history. An agent can route without inferring anything.

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