holonovel

Adventure Management

manage_adventure

Destructive

Generate, load, or list TTRPG adventure content; mutating actions persist to your novel and can be reverted with manage_history undo.

Instructions

Generate, load, or list adventure content. 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). generate defaults target to novel when one is active; a !force prefix bypasses the guard. Use when: the GM wants a new adventure scaffold, a single encounter, or to load a prepared module. Do NOT use when: recording a story beat — use manage_story (action: record).

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	Adventure module slug (load).
`action`	Yes	generate, generate_encounter, load, or list.
`filter`	No	Optional genre filter (list).
`target`	No	novel, codex, or both (generate).
`context`	No	Scene context (generate_encounter).
`premise`	No	Adventure premise (generate).

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.

Addedv1.0.3Sep 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructive=true, non-idempotent, not read-only. The description adds real value beyond them: mutating actions 'persist to the Novel and are audited', read-only actions do not mutate, and the undo route is specified. It stops short of describing what persisted state looks like or what 'audited' implies operationally.

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-loaded with the core capability, then structured into mutation semantics, revert path, and explicit use/do-not-use guidance. Dense but each clause carries a distinct rule; no obvious filler, though it is longer than strictly necessary.

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?

With an output schema present, return values need not be explained. The description covers mutation persistence, undo, default target behavior, the force bypass, and sibling routing — everything an agent needs to invoke this multi-action tool correctly.

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 coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: generate defaults target to novel when one is active, and a '!force' prefix bypasses the guard. Those are behavioral rules for parameters not encoded anywhere in the schema.

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?

Opens with a specific verb set and resource ('Generate, load, or list adventure content') and immediately scopes each action into mutating vs read-only. It also names the siblings it is distinct from (manage_history, manage_story), so an agent can route without opening other schemas.

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?

Explicitly provides 'Use when' (GM wants a scaffold, single encounter, or to load a module) and 'Do NOT use when' (recording a story beat → manage_story). It also names the revert path via manage_history, giving complete routing guidance.

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