Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_helpdesk_tree

Lists the Knowledge Base file tree to discover valid tree_path values for file operations; use sub_path to traverse deeper only when specific content is requested.

Instructions

Lists the Knowledge Base file tree. Use it to discover valid tree_path values for file operations. Recursive traversal is needed to descend deeper in the tree, using the sub_path argument. Descend only if the user asks for a particular content.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_helpdesk_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe Knowledge Base locale code (eg. 'en' for English).en
sectionNoThe Knowledge Base section (for traditional articles: 'articles').articles
sub_pathNoThe sub-path on the Knowledge Base tree (file or directory).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the recursive-traversal model and a cost-limiting rule for descending, which is genuinely useful. It omits permission requirements, whether results are paginated or truncated, and the shape of the returned tree.

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?

Three short sentences, front-loaded with the core action, then purpose, then the traversal caveat. Nothing is redundant, though the final sentence's phrasing ('a particular content') is slightly awkward.

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 three-parameter read tool with no output schema and no annotations, the description covers intent and recursion but says nothing about what the returned tree looks like (paths only? titles? nested structure?) or how locale/section affect the result. Adequate, not complete.

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 and section are already documented; the description only adds meaning for sub_path (the recursion handle). It also introduces the term 'tree_path' that does not match the schema's 'sub_path', which could cause a mild mapping confusion rather than clarifying it.

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 and resource ('Lists the Knowledge Base file tree') and adds the practical goal ('discover valid tree_path values for file operations'), which separates it from content/metadata getters. It does not explicitly name a sibling alternative such as search_helpdesk_tree, so it stops short of full differentiation.

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

Usage Guidelines4/5

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

Gives clear when-to-use guidance (path discovery before file operations) and a when-not-to constraint ('Descend only if the user asks for a particular content'), which prevents unnecessary deep traversal. No explicit mention of search_helpdesk_tree as the alternative for content lookup, which would be the missing fifth point.

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