Skip to main content
Glama

Ruleset Package Management

manage_ruleset
Destructive

Search an installed ruleset index, install or remove packages, list packages, bind a Novel to a ruleset, and import or remove supplementary Wisdom to control game rules and content.

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_context (action: discover).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_ruleset"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoDeterministic seed (roll).
slugNoRuleset slug (install/remove/bind/import_supplementary/remove_supplementary).
indexNoSearch index (install).
modelNoExtraction model (install).
queryNoSearch query (search).
tableNoGeneration table to roll on (roll).
toolsNoTool schemas (install).
actionYessearch, install, remove, list, bind, import_supplementary, or remove_supplementary.
sourceNoSupplementary Markdown source path (import_supplementary).
wisdomNoInline supplementary Wisdom items (import_supplementary).
promptsNoPrompts (install).
manifestNoPackage manifest (install).
resourcesNoResources (install).
max_resultsNoMaximum results (search).

Output Schema

NameRequiredDescriptionDefault
textNoHuman-readable text envelope mirroring the structured result (REQ-001, REQ-548a).
statusYesMachine-readable result status: OK, NEED_INPUT, WARNING, PARTIAL, or an error category (REQ-002, REQ-548c).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.10.15
    • 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"
      +]
  2. Changed3 schema fields changedv2026.10.13
    • 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"
      +}
  3. Changed2 schema fields changed
    • 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"
      +]
  4. Addedv1.0.3

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), the description discloses which actions are read-only versus state-mutating, that mutations are audited and reversible via the paired action, that installing an existing slug conflicts, and that remove refuses while a Novel is bound. Those preconditions and audit/reversal traits are not inferable from the annotation flags.

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?

Content is dense and front-loaded: the operation inventory comes first, per-action behavior second, then routing rules. The opening sentence is very long and packs multiple actions together, but every clause carries information and nothing is redundant padding.

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?

For a 14-parameter multi-action tool with an output schema, the description covers each action's side effects, conflict/refusal conditions, and fallback behavior for supplementary Wisdom. Minor gaps remain: it does not say which parameters apply to the list or bind actions, and it does not mention result limits for search despite a max_results parameter.

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 already 100%, so the baseline is 3, but the description adds real meaning: import_supplementary prefers inline 'wisdom' and only falls back to 'source' when inline data is absent, and it states that search is scope-independent of an active Novel. It also usefully notes that seed/table belong to resolve_mechanic rather than this tool, though it never explains what 'list' or 'bind' require or covers max_results.

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 each operation precisely: search an installed index, install/remove a package, list installed packages, bind a Novel, import/remove supplementary Wisdom. It also separates its scope from siblings by naming resolve_mechanic for table rolls and manage_context (discover) for unknown ruleset names, so an agent can place it 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 has explicit 'Use when' and 'Do NOT use when' sections, including a concrete redirect ('ruleset name is unknown — use manage_context (action: discover)') and a second redirect for table rolls to resolve_mechanic. That is exactly the when/when-not/alternative triad.

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