holonovel

World Model Management

manage_world

Destructive

Create, update, remove, or bulk-convert rooms, things, and exits in a persistent world model. Mutations are audited; undo the latest change with manage_history.

Instructions

Manage the world model — rooms, things, and exits. 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). create_thing honors location_type only when location is set; kind forces property defaults. Use when: creating, updating, removing, or bulk-converting locations and objects. Do NOT use when: navigating the world — use run_command (action: execute) or run_command (action: resolve).

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Destination room alias for room_b (create_exit).
`key`	No	Bound key thing name required to unlock or lock this thing when lockable (create_thing/update_thing).
`lit`	No	When true the thing is lit (create_thing/update_thing).
`from`	No	Source room alias for room_a (create_exit).
`kind`	No	Optional thing kind (create_thing).
`name`	No	Room/thing name (create/update/remove).
`room`	No	Source room (create_exit/remove_exit).
`seed`	No	Deterministic seed (generate).
`fixed`	No	When true the thing cannot be taken (create_thing/update_thing).
`action`	Yes	create_room, update_room, remove_room, create_thing, update_thing, remove_thing, create_exit, remove_exit, convert, or generate.
`edible`	No	When true the thing can be eaten (create_thing/update_thing).
`locked`	No	When true the thing starts locked (create_thing/update_thing).
`room_a`	No	Source room (create_exit).
`room_b`	No	Destination room (create_exit).
`source`	No	Hybrid world-model source text (convert).
`location`	No	Optional containing room or thing (create_thing/update_thing).
`lockable`	No	When true the thing can be locked (create_thing/update_thing).
`openable`	No	When true the thing can be opened (create_thing/update_thing).
`readable`	No	When true the thing can be read (create_thing/update_thing).
`wearable`	No	When true the thing can be worn (create_thing/update_thing).
`climbable`	No	When true the thing can be climbed (create_thing/update_thing).
`direction`	No	Direction (create_exit/remove_exit).
`drinkable`	No	When true the thing can be drunk (create_thing/update_thing).
`enterable`	No	When true the thing can be entered (create_thing/update_thing).
`read_text`	No	Text revealed when the thing is read (create_thing/update_thing).
`switchable`	No	When true the thing can be switched (create_thing/update_thing).
`description`	No	Optional description (create/update).
`switched_on`	No	When true the thing is switched on (create_thing/update_thing).
`transparent`	No	When true the thing is transparent (create_thing/update_thing).
`location_type`	No	Where the thing is placed (create_thing).

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.

Changed3 schema fields changedv1.0.4Sep 30, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "Source room alias for room_a (create_exit).",
+  "type": "string"
+}

addedInput schema / properties / key

Added value: +{
+  "description": "Bound key thing name required to unlock or lock this thing when lockable (create_thing/update_thing).",
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Destination room alias for room_b (create_exit).",
+  "type": "string"
+}

Addedv1.0.3Sep 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), it discloses that mutating actions persist to the Novel and are audited while read-only actions do not mutate state, and it names the exact undo route. That is meaningful behavioral context the annotations cannot express.

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?

Reasonably sized for a 10-action, 30-parameter tool, with purpose and persistence semantics front-loaded. Some clauses are dense run-ons ('create_thing honors location_type only when location is set; kind forces property defaults'), but every sentence 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?

An output schema exists so return values need no explanation, and the description covers mutation semantics, undo, and routing. It stops short of clarifying the convert/generate actions, which are the least self-explanatory members of the action enum.

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 the baseline is 3; the description adds real meaning on top by stating that create_thing honors location_type only when location is set and that kind forces property defaults. It does not explain the convert/generate semantics or the mutual exclusion of room_a/room_b/from/to pairs.

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?

Names the specific resource ('the world model — rooms, things, and exits') and the operations (create, update, remove, bulk-convert). It explicitly contrasts itself with run_command for navigation, so an agent can separate it from siblings without opening the 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?

Contains an explicit 'Use when' clause (creating, updating, removing, bulk-converting locations and objects) and a 'Do NOT use when' clause routing navigation to run_command (execute/resolve). It also names the recovery path (manage_history action: undo).

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