Skip to main content
Glama
Polloinfilzato

DM20 Protocol

by Polloinfilzato
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

disable_library_source

Remove a library source from the current campaign's enabled content to prevent its use in gameplay.

Instructions

Disable a library source for the current campaign.

Removes a library source from the campaign's enabled content. The source will no longer be available for use in this campaign.

Args: source_id: The source identifier (use list_enabled_library to see enabled sources)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_idYesThe source identifier to disable

Implementation Reference

  • src/dm20_protocol/storage.py:1324-1339 (handler)
    The `disable_library_source` method in `DnDStorage` class handles disabling a library source for the active campaign. It updates the `_library_bindings` object and saves the updated bindings to disk.
    def disable_library_source(self, source_id: str) -> None:
    """Disable a library source for the current campaign.

    Args:
        source_id: The source identifier to disable
    """
    if not self._current_campaign:
        raise ValueError("No current campaign")

    if not self._library_bindings:
        raise ValueError("Library bindings not initialized")

    self._library_bindings.disable_source(source_id)
    self._save_library_bindings()
    logger.info(f"🚫 Disabled library source '{source_id}' for campaign '{self._current_campaign.name}'")
  • src/dm20_protocol/permissions.py:182-182 (registration)
    The `disable_library_source` tool is registered in the `_DM_ONLY_TOOLS` set within `src/dm20_protocol/permissions.py`, restricting its usage to the Dungeon Master (DM) role.
    "disable_library_source",

Tool Definition Quality

A3.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the effect ('removes a library source', 'will no longer be available'), but lacks details on permissions required, whether the action is reversible, error conditions, or rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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 front-loaded with the core purpose, followed by clear explanations of effects and parameter usage. Every sentence adds value without redundancy, and the structure is efficient with zero waste.

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 the tool's complexity (a mutation with no annotations or output schema), the description covers the basic purpose and parameter semantics adequately but lacks behavioral details like error handling or confirmation of success. It is minimally viable but has clear gaps in transparency.

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?

The schema description coverage is 100%, so the schema already documents the single parameter 'source_id'. The description adds value by explaining what 'source_id' represents and referencing 'list_enabled_library' to obtain valid values, providing practical guidance beyond the schema's basic definition.

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 clearly states the specific action ('Disable'), resource ('a library source'), and context ('for the current campaign'), distinguishing it from siblings like 'enable_library_source' and 'list_enabled_library'. It precisely explains what the tool does without being vague or tautological.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool (to remove a library source from a campaign's enabled content) and references 'list_enabled_library' as a prerequisite for obtaining source identifiers. However, it does not explicitly state when not to use it or compare it to alternatives like 'unload_rulebook' or 'delete_campaign'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Polloinfilzato/dm20-protocol'

If you have feedback or need assistance with the MCP directory API, please join our Discord server