holonovel

World

world

Manage game world locations and objects by creating, updating, removing, or converting rooms, things, and exits.

Instructions

Manage the world model — rooms, things, and exits. Use when: creating, updating, removing, or bulk-converting locations and objects. Do NOT use when: navigating the world — use command (action: execute) or command (action: resolve).

Input Schema

TableJSON Schema

Name	Required	Description
`lit`	No	When true the thing is lit (create_thing/update_thing).
`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).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.0.2Sep 9, 2026

changedInput schema / properties / action / description

Previous value: -"create_room, update_room, remove_room, create_thing, update_thing, remove_thing, create_exit, remove_exit, or convert."New value: +"create_room, update_room, remove_room, create_thing, update_thing, remove_thing, create_exit, remove_exit, convert, or generate."

changedInput schema / properties / action / enum

Previous value: -[
-  "create_room",
-  "update_room",
-  "remove_room",
-  "create_thing",
-  "update_thing",
-  "remove_thing",
-  "create_exit",
-  "remove_exit",
-  "convert"
-]New value: +[
+  "create_room",
+  "update_room",
+  "remove_room",
+  "create_thing",
+  "update_thing",
+  "remove_thing",
+  "create_exit",
+  "remove_exit",
+  "convert",
+  "generate"
+]

addedInput schema / properties / seed

Added value: +{
+  "description": "Deterministic seed (generate).",
+  "type": "string"
+}

AddedSep 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only mark readOnlyHint false; the description adds that operations include destructive changes like 'removing' and conversions, making mutating behavior explicit. No contradiction with the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence plus two use-condition clauses, front-loading the action and alternatives. It avoids listing parameters, which are handled by the schema.

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?

The description plus fully annotated schema gives enough context to select and invoke actions correctly. It omits return-value details, but the operations are straightforward mutations; still, without an output schema, a brief note on result would improve completeness.

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?

All 27 parameters have schema descriptions, and most parenthetical notes indicate which action consumes them (e.g., 'create_exit/remove_exit'). Some terms such as 'hybrid world-model source text' and allowed directions are still vague, so it does not reach 5.

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 names specific actions ('creating, updating, removing, or bulk-converting') and the managed resource ('world model — rooms, things, and exits'), making its purpose unmistakable. It also distinguishes it from 'command (action: execute/resolve)' for navigation, so an agent can pick it among siblings.

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 explicitly states 'Use when' for CRUD/convert operations and 'Do NOT use when' for navigation, pointing to command action execute/resolve. This gives clear selection criteria.

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

Deploy Server

World

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools