Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

delete_helpdesk_tree_path

Deletes a Knowledge Base file at a specified tree path in Crisp Helpdesk. Use it to remove an outdated or unwanted article file after confirming the exact path and locale.

Instructions

Deletes the Knowledge Base file at the specified tree_path. Confirm the intended file and path before calling.

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": {
      "tree_path": "<tree_path>"
    },
    "name": "delete_helpdesk_tree_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe Knowledge Base locale code (eg. 'en' for English).en
sectionNoThe Knowledge Base section (for traditional articles: 'articles').articles
tree_pathYesThe file path on the Knowledge Base tree (Markdown file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that the operation is destructive and advises verification, but says nothing about whether deletion is permanent, whether deleting a tree_path removes descendant nodes, what permissions are required, or what the caller gets back. For an irreversible mutation these are significant undisclosed traits.

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?

Two short sentences with zero padding: the action and target come first, the caution second. Nothing is redundant and nothing competes for attention.

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?

The core contract (delete this file at this path) is unambiguous and the schema covers all three parameters. But for a destructive tool with no annotations and no output schema, the description leaves the agent guessing about reversibility, recursion into sub-paths, and failure modes.

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%, so locale, section, and tree_path are all documented in the schema, and the baseline of 3 applies. The description only echoes tree_path and adds no format or path-syntax detail beyond what the schema already states.

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 names a specific verb ('Deletes') and resource ('Knowledge Base file at the specified tree_path'), which cleanly separates it from the create_/update_/get_ siblings in the catalog. It stops short of explicitly naming a contrasting alternative, so it lands at clear-but-not-differentiated.

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

Usage Guidelines3/5

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

There is a real precondition ('Confirm the intended file and path before calling'), which is useful safety guidance for a destructive operation. However, it gives no when-not guidance, no mention of the read-before-delete siblings (get_helpdesk_tree_path_content / get_helpdesk_tree_path_metadata) that an agent would naturally use to verify the target.

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