Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_helpdesk_tree_path_content

Retrieve the content of a Knowledge Base Markdown file by its tree path, with optional locale and section settings, to read helpdesk articles directly.

Instructions

Returns 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>"
    },
    "name": "get_helpdesk_tree_path_content"
  }
}

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.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails to: it does not say the content is Markdown, whether missing paths error or return empty, how large files are handled, or whether the operation is read-only. Only the schema's enum/default hints at locale and section behavior.

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 no filler. Nothing is wasted or buried.

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 simple read tool this is close to adequate, but with no output schema and no annotations the description should describe what is returned (a content string vs. a structured object) and what happens for invalid paths. Those gaps matter more here because structured fields provide no coverage.

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%, with locale, section, and tree_path each documented in the schema itself. The description adds no meaning beyond restating that tree_path identifies the file, so the baseline of 3 is appropriate.

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 ('Returns the content of the Knowledge Base file') and scopes it to 'the specified tree_path'. The word 'content' implicitly distinguishes it from the metadata/title siblings, though it never names them.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the read-content tool, but nothing tells it when to prefer this over get_helpdesk_tree_path_metadata or get_helpdesk_tree_path_title, nor any prerequisites such as needing the path to exist first.

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