Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_helpdesk_tree_path_title

Retrieves the title of a Knowledge Base file at a given tree_path, helping you identify the correct helpdesk article by path, section, and locale.

Instructions

Returns the title 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>"
    },
    "name": "get_helpdesk_tree_path_title"
  }
}

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.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does establish that this is a read returning a single field. However, it says nothing about behavior when the tree_path does not exist, how locale affects the returned title, or whether permissions are required.

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?

A single front-loaded sentence with zero filler that states exactly what comes back and the key input. Nothing is redundant or buried.

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 simple single-value getter with fully documented parameters and no output schema, the description covers the essential contract. Only edge-case behavior (missing path, locale resolution) is left unaddressed.

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 the schema already explains tree_path, locale, and section, giving a baseline of 3. The description only echoes tree_path and adds no meaning for locale fallback or the fixed 'articles' section.

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 ('Returns') and resource ('the title of the Knowledge Base file') scoped by 'tree_path', which clearly separates it from get_helpdesk_tree_path_content or get_helpdesk_tree_path_metadata. It does not explicitly name those siblings, so differentiation is inferable rather than stated.

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 call this versus the sibling getters, no prerequisites, and no conditions under which to prefer the metadata or content tools. The only implied usage is 'you want the title', which the agent must infer from the name alone.

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