Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

update_helpdesk_tree_path_content

Update the Markdown content of a Knowledge Base file at a specified tree path, with locale and section options, to keep helpdesk articles accurate.

Instructions

Updates the content of the Knowledge Base file at the specified tree_path.

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>",
      "content": "<content>"
    },
    "name": "update_helpdesk_tree_path_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe Knowledge Base locale code (eg. 'en' for English).en
contentYesThe new content of the tree path (in Markdown format).
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

C2.9/5.0
Behavior2/5

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

With no annotations present, the description carries the full behavioral burden and discloses very little. It does not say whether the existing content is fully overwritten or merged, whether permissions or auth are required, or what happens if the tree_path or locale does not exist.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, but the brevity is close to the point of under-specification for a mutation tool rather than a model of tight writing.

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

Completeness2/5

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

This is a content-mutating operation with no annotations and no output schema, so the description must explain overwrite semantics, preconditions, and the effect of locale/section. None of that is present, leaving the agent to guess at the consequences of the call.

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 tree_path, content, locale, and section, establishing the baseline of 3. The description adds only the phrase 'at the specified tree_path', which gives no format, path syntax, or targeting semantics beyond the schema.

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 (updates) and resource (content of the Knowledge Base file), and the tree_path scope separates it from tree-wide operations. It implicitly distinguishes itself from the sibling update_helpdesk_tree_path_title by naming 'content' rather than title, though it never makes that distinction explicit.

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?

There is no when-to-use guidance: nothing says to use this instead of update_helpdesk_tree_path_title when renaming, or instead of create_helpdesk_tree_path when the file does not exist. The agent must infer the choice from tool names alone.

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