NexTool MCP for GLPI

Delete knowledge base category

glpi_delete_knowbase_category

DestructiveIdempotent

Permanently delete a GLPI knowledge base category by ID, with a required reason for the audit trail. Use it to remove obsolete categories from the knowledge base.

Instructions

Permanently delete a knowledge base category.

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": {
      "categoryId": "<categoryId>",
      "reason": "<reason>"
    },
    "name": "glpi_delete_knowbase_category"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	Yes	Why this item is being deleted (audit trail, required)
`categoryId`	Yes	Item ID

Output Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.2Oct 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered. The description adds 'Permanently', which clarifies irreversibility beyond the destructive hint, but it omits other useful context such as whether deletion cascades to child items or requires special permissions.

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, front-loaded sentence with no wasted words. It states the core action clearly and immediately.

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?

Given the simple delete operation, rich annotations, complete parameter schema, and presence of an output schema, the description is nearly sufficient. It could mention the mandatory audit reason or the permanence of deletion more explicitly, but those are covered by structured fields.

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 both parameters, including the required 'reason' for audit trail. The description adds no additional parameter meaning or formatting details, making the baseline 3 appropriate.

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 states a specific verb ('delete') and resource ('knowledge base category') and adds the scope modifier 'permanently'. It distinguishes the tool from sibling operations on knowledge base items (e.g., glpi_delete_knowbase_item) by naming the category resource, but does not explicitly differentiate from other category tools like update or create.

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?

The description provides no guidance on when to use this tool versus alternatives, such as glpi_delete_knowbase_item or glpi_update_knowbase_category. It simply restates the operation without context about prerequisites, exclusions, or the required audit reason.

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

Deploy Server