Skip to main content
Glama
Sign In
DM20 Protocol

DM20 Protocol

by Polloinfilzato
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unload_rulebook

Remove a specific rulebook from your current D&D campaign to manage game resources and streamline gameplay.

Instructions

Remove a rulebook from the current campaign.

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": {
      "source_id": "<source_id>"
    },
    "name": "unload_rulebook"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYesID of the rulebook to unload (from list_rulebooks)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the action ('Remove') without disclosing behavioral traits like whether this is reversible, requires permissions, affects game state, or has side effects. It lacks details on what 'unload' entails operationally.

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 a single, clear sentence with zero wasted words, front-loading the key action and resource. It's appropriately sized for a simple tool with one parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter with full schema coverage and no output schema, the description is minimally adequate but lacks context on behavior, alternatives, or effects. For a mutation tool with no annotations, it should provide more operational details to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the single parameter 'source_id' with its description. The tool description adds no additional meaning about parameters beyond what the schema provides, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Remove') and resource ('a rulebook from the current campaign'), making the purpose evident. It doesn't explicitly differentiate from sibling tools like 'disable_library_source' or 'unload_adventure', but the specificity of 'rulebook' and 'current campaign' provides reasonable distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'disable_library_source' or 'unload_adventure', nor any prerequisites (e.g., requiring a loaded rulebook first). The description assumes context without stating when it's appropriate.

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

Deploy Server

Other Tools