Skip to main content
Glama

Delete a knowledge hub

delete_knowledge_hub
DestructiveIdempotent

Use this when the user wants a knowledge hub and all its pages deleted for good. The default hub cannot be deleted until another hub is made the default. It cannot be restored. Free.

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": {
      "hubId": "<hubId>"
    },
    "name": "delete_knowledge_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe knowledge hub's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds genuinely non-structured behavior: irreversible deletion ("cannot be restored"), cascade to all contained pages, a blocking precondition for default hubs, and no cost ("Free"). Those are exactly the traits an agent needs before committing to an irreversible write.

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 trigger and no wasted clauses; three short sentences each carry distinct information (scope, precondition, irreversibility). The telegraphic fragments "It cannot be restored." and "Free." slightly hurt readability but not substance.

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 one-parameter destructive tool with full annotation and schema coverage and no output schema, the description covers scope, precondition, and irreversibility. It does not mention whether dependent artifacts (e.g. campaigns referencing the hub) are affected, a minor remaining gap.

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 coverage is 100% and hubId already carries a description with a 24-char hex pattern, so the schema does the heavy lifting. The description adds only that the target is a hub id, with no guidance on where to obtain one or what to do if it references the default hub beyond the deletion precondition.

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?

States a specific verb and resource ("a knowledge hub and all its pages deleted"), and the cascade scope separates it from delete_knowledge_hub_page without naming it. It stops short of explicitly routing the agent away from the page-level sibling, so a 4 rather than a 5.

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?

Opens with an explicit trigger condition ("Use this when the user wants a knowledge hub and all its pages deleted for good") and supplies a precondition the agent must check first: the default hub cannot be deleted until another hub is made default. No explicit exclusions or named alternatives are given, which keeps it at 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources