Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_helpdesk_pages

Lists published Knowledge Base page URLs and their tree paths so you can locate helpdesk articles by locale. Use it to find pages before file operations, or prefer the tree tool to discover tree_path values.

Instructions

Lists published Knowledge Base page URLs and their tree paths. Prefer the list_helpdesk_tree tool to discover tree_path values for file operations.

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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe Knowledge Base locale code (eg. 'en' for English).en
sectionNoThe Knowledge Base section (for traditional articles: 'articles').articles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/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 behavioral burden. It usefully discloses that only published pages are returned, but says nothing about pagination, result limits, ordering, or auth requirements for a list operation that could return many pages.

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 sentences with zero filler. The capability statement is front-loaded and the routing hint follows, so the agent gets purpose first and alternative second.

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 read-only two-optional-parameter list tool with no output schema, the description covers what is returned (URLs and tree paths) and how it differs from the main alternative. The only gap is the absence of any volume or pagination expectations for a listing that can grow large.

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% and both parameters (locale, section) are documented inline with defaults and an enum, so the schema already does the heavy lifting. The description adds no additional meaning about how locale or section affect the result set, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it lists published Knowledge Base page URLs together with their tree paths. It also explicitly distinguishes itself from the sibling list_helpdesk_tree, so an agent can separate the two without opening either schema.

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?

It gives explicit routing guidance: prefer list_helpdesk_tree when the goal is to discover tree_path values for file operations, which implicitly positions this tool as the URL-listing option. It does not state an explicit 'use this when' condition for this tool itself, which keeps it short of a 5.

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