holonovel

Synthesis Management

manage_synthesis

Destructive

Run, revert, list, activate, or toggle synthesis items (voice examples, lore templates, action patterns). Mutations persist and are audited; read-only actions do not change state.

Instructions

Manage synthesis content (voice examples, lore templates, action patterns, and other Ruleset Wisdom). 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). activate/deactivate with key omitted act on the whole module. Use when: running, reverting, listing, activating, deactivating, toggling, or player-authoring synthesis items. Do NOT use when: browsing the codex — use manage_codex (action: list).

Input Schema

TableJSON Schema

Name	Required	Description
`key`	No	Item key (activate: number; player_add/player_remove: string).
`force`	No	Re-run even if unchanged (run).
`action`	Yes	run, revert, list, activate, deactivate, toggle, toggle_action, player_add, player_remove, or player_list.
`detail`	No	Return full entries (list).
`module`	No	Synthesis module (activate/deactivate/toggle/player_*/list).
`content`	No	Item content (player_add).
`enabled`	No	Enable or disable (toggle).
`triggers`	No	Recall triggers (player_add).
`badge_scope`	No	shared or player (player_add).

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.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real context beyond them: mutating actions persist to the Novel and are audited, read-only actions leave state untouched, and omitting key on activate/deactivate acts on the whole module. It stops short of mapping each action to its individual destructive/read-only nature, which would be the full picture.

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?

Front-loaded with purpose, then a compact behavioral clause, then explicit when/when-not guidance. Every sentence carries routing or behavioral information; the parenthetical content-type list is the only mildly expendable element.

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 no explanation. The description covers persistence, audit trail, whole-module semantics, revert path, and sibling exclusions — everything needed to invoke a 10-action, 9-parameter 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 a genuinely non-obvious semantic: activate/deactivate with key omitted operate on the whole module. It also points to manage_history (action: undo) as the revert mechanism, adding meaning beyond the enum listing.

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?

States a specific verb (manage) and resource (synthesis content), then enumerates the concrete content types it covers (voice examples, lore templates, action patterns, Ruleset Wisdom). It explicitly routes non-matching cases to siblings (manage_codex, manage_history), so an agent can distinguish it without opening a 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?

Explicit 'Use when:' list of actions and a 'Do NOT use when: browsing the codex — use manage_codex (action: list)' exclusion. It also names manage_history (action: undo) as the revert path, giving both positive and negative routing.

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