holonovel

Ruleset Package Management

manage_ruleset

Destructive

Manage ruleset packages by searching installed indexes, installing or removing packages, listing packages, binding Novels to rulesets, and importing or removing supplementary Wisdom.

Instructions

Manage ruleset packages: search an installed ruleset's index, install or remove a package, list installed packages, bind a Novel to a ruleset, or import/remove supplementary Wisdom. search accepts an optional slug, works with no active Novel, and is read-only; install, remove, import_supplementary, and remove_supplementary mutate state, are audited, and are reversible via the paired action. install of an existing slug conflicts, and remove refuses while a Novel is bound to that slug. binding scopes only Novel-dependent features; import_supplementary uses inline wisdom when present and reads source only when absent. Table rolls are resolve_mechanic (action: roll). Use when: searching rules content, managing packages, binding a Novel, or adding/removing supplementary Wisdom. Do NOT use when: the ruleset name is unknown — use manage_session (action: discover).

Input 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, 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

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.

Changed2 schema fields changedv2026.10.15Oct 25, 2026
- removedInput schema / properties / wisdom / items / properties / key / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / wisdom / items / properties / key / type
```
Added value: +[
+  "string",
+  "number"
+]
```
Changed3 schema fields changedv2026.10.13Oct 25, 2026
- addedInput schema / properties / wisdom / items / properties / quoted_excerpt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / wisdom / items / properties / source_snapshot
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / wisdom / items / properties / source_url
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / action / description

Previous value: -"search, install, remove, list, bind, roll, import_supplementary, or remove_supplementary."New value: +"search, install, remove, list, bind, import_supplementary, or remove_supplementary."

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "install",
-  "remove",
-  "list",
-  "bind",
-  "roll",
-  "import_supplementary",
-  "remove_supplementary"
-]New value: +[
+  "search",
+  "install",
+  "remove",
+  "list",
+  "bind",
+  "import_supplementary",
+  "remove_supplementary"
+]

Addedv1.0.3Sep 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations it discloses per-action safety: search is read-only and needs no active Novel; mutating actions are audited and reversible via the paired action; install of an existing slug conflicts; remove refuses while a Novel is bound; binding scopes only Novel-dependent features. These are exactly the behavioral traits annotations cannot express per-action, and they do not contradict the tool-level destructiveHint.

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?

Despite covering seven actions and fourteen params, it is tightly organized: purpose first, then per-action behavior and constraints, then Use-when/Do-not-use routing. Every sentence carries actionable information with no filler.

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 handling return values and annotations covering the safety profile, the description fills the remaining gaps: per-action semantics, mutation/audit/reversibility, conflict and refusal conditions, and routing to siblings. An agent has everything needed to pick the right action 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 the schema already documents each parameter and its target action, warranting a baseline 3. The description adds genuine value beyond that by noting that search accepts an optional slug (info not present in the schema's slug description), though it does not clarify the remaining install-specific params.

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 enumerates the concrete actions verb+resource (search, install, remove, list, bind, import/remove supplementary Wisdom) in one front-loaded sentence, so an agent can map the tool to its tasks precisely. It also distinguishes itself from resolve_mechanic (rolls) and manage_session (discovery).

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 gives an explicit 'Use when:' list and a 'Do NOT use when:' exclusion that names the alternative ('the ruleset name is unknown — use manage_session (action: discover)'). It further routes table rolls to resolve_mechanic, leaving nothing to inference.

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