Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

update_helpdesk_tree_path_title

Updates the title stored in a Knowledge Base file's metadata at the specified tree path, enabling helpdesk article renaming by locale.

Instructions

Updates the title in the metadata 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>",
      "title": "<title>"
    },
    "name": "update_helpdesk_tree_path_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesThe new title of the tree path.
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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does clarify the change is scoped to the title in metadata (not the body content), but it says nothing about required permissions, whether the rename is reversible, what happens on a nonexistent tree_path, or what is returned.

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; the target resource and the mutated field appear before the qualifier. Nothing is redundant, though it is too short to earn a 5.

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?

For a 4-parameter mutation with no annotations and no output schema, the definition is minimally viable: the schema fully specifies inputs, but the description omits return behavior, error conditions, and permission requirements that an agent needs before invoking a write.

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 every parameter is documented in-schema, so the baseline is 3. The description echoes tree_path and title but adds no semantics for locale or section 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?

States a specific verb ('Updates') and a specific resource ('the title in the metadata of the Knowledge Base file'), and the 'title' vs 'metadata' framing implicitly separates it from the content-editing sibling. It does not explicitly name update_helpdesk_tree_path_content, so differentiation is left to inference.

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 guidance on when to use this versus the closely related update_helpdesk_tree_path_content or the metadata getter, and no statement of prerequisites (permissions, whether the tree_path must already exist). Usage is only inferable from the verb itself.

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