holonovel

Ruleset Package Management

manage_ruleset

Destructive

Search, install, remove, or list ruleset packages; bind a Novel to a ruleset; roll generation tables; and import or remove supplementary Wisdom for tabletop RPG play.

Instructions

Manage ruleset packages: search a bound ruleset's index, install or remove a package, list installed packages, bind a Novel to a ruleset, roll on a generation table, or import/remove a supplementary ruleset. import_supplementary uses inline wisdom when present and reads source only when absent. install/remove are reversible via the paired action; roll and search are read-only. Use when: searching rules content, installing/removing/listing packages, binding a Novel, rolling a table (roll), or adding/removing supplementary Wisdom (import_supplementary/remove_supplementary). Do NOT use when: the Novel is ruleset-free — use run_command (action: suggest) or manage_session (action: health). install/remove/import_supplementary/remove_supplementary mutate state and are audited; search and roll are read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`seed`	No	Deterministic seed (roll).
`slug`	No	Ruleset slug (install/remove/bind/import_supplementary/remove_supplementary).
`index`	No	Search index (install).
`model`	No	Extraction model (install).
`query`	No	Search query (search).
`table`	No	Generation table to roll on (roll).
`tools`	No	Tool schemas (install).
`action`	Yes	search, install, remove, list, bind, roll, import_supplementary, or remove_supplementary.
`source`	No	Supplementary Markdown source path (import_supplementary).
`wisdom`	No	Inline supplementary Wisdom items (import_supplementary).
`prompts`	No	Prompts (install).
`manifest`	No	Package manifest (install).
`resources`	No	Resources (install).
`max_results`	No	Maximum results (search).

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 declare destructiveHint=true globally, which is misleading for a tool that mixes reads and writes; the description usefully corrects this by stating search and roll are read-only, install/remove are reversible via the paired action, and the mutating actions are audited. It stops short of describing failure modes or prerequisites for bind/install beyond the reversible pairing.

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 operation list and kept tight, but the first sentence's action enumeration is largely repeated in the 'Use when' clause, creating mild redundancy across an otherwise efficient block.

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?

For a 14-parameter, 8-action tool with an output schema and full annotation coverage, the description supplies everything an agent needs to choose the right action: action semantics, read vs write behavior, alternative tools for the excluded case, and the wisdom/source precedence rule. Return values are covered by the output schema, so nothing material is missing.

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, but the description adds a genuine cross-parameter rule: import_supplementary prefers inline 'wisdom' and only reads 'source' when wisdom is absent. That behavior is not derivable from the per-parameter schema text, though the remaining 13 parameters get no added explanation.

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 a specific resource (ruleset packages) and enumerates the concrete operations: search an index, install/remove a package, list installed packages, bind a Novel, roll a generation table, and import/remove supplementary rulesets. This lets an agent distinguish it from the many manage_* 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?

It provides explicit 'Use when' conditions mapped to specific actions and a 'Do NOT use when' clause naming two concrete alternatives (run_command with action: suggest, manage_session with action: health) for the ruleset-free case. This is textbook when/when-not/alternative routing.

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