Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

search_helpdesk_tree

Locate a Knowledge Base file by title when its path is unknown. Filters the expanded helpdesk tree by search query, so no recursive traversal is needed.

Instructions

Searches the expanded Knowledge Base file tree by file title. Use it to locate a file when its path is unknown; no recursive traversal is needed.

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": {
      "search_query": "<search_query>"
    },
    "name": "search_helpdesk_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe Knowledge Base locale code (eg. 'en' for English).en
sectionNoThe Knowledge Base section (for traditional articles: 'articles').articles
search_queryYesThe search query to filter Knowledge Base tree files by (eg. a title).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/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 disclosure burden; it does signal that this is a read-only lookup over a pre-"expanded" tree, hinting at a prerequisite state. It does not say whether matching is exact, substring, or fuzzy, how results are ordered or capped, or whether multiple matches can be returned — all relevant for a search tool.

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 the capability first and the routing condition second; every clause carries information and nothing is padded.

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 three-parameter, single-purpose read lookup with a fully described schema, the definition covers what it does and when to reach for it. The remaining gap is result behavior (match semantics, whether the tree must be expanded first), which matters more here because there is no output schema to describe returns.

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 all three parameters are already documented, and the baseline of 3 applies. The description's "by file title" slightly narrows how search_query should be populated (a title, not a path or full-text), but adds nothing about locale or 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?

"Searches the expanded Knowledge Base file tree by file title" names a specific verb, resource, and matching field, which separates it from path-based siblings like get_helpdesk_tree_path_content and list_helpdesk_tree. It stops short of naming any sibling explicitly, so the differentiation is inferred 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 Guidelines4/5

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

"Use it to locate a file when its path is unknown" gives a clear triggering condition, and "no recursive traversal is needed" rules out a manual walk of the tree. It implies but never states the complement (use the get_*_path_* tools when the path is already known), so there is no explicit named alternative.

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