Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_helpdesk_locales

Lists configured Knowledge Base locales and their public URLs so you can identify available helpdesk language versions.

Instructions

Lists the configured Knowledge Base locales and their public URLs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/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 burden; it does at least convey that this is a non-mutating enumeration and that the elements include a public URL field, which is useful output context given no output schema. It omits ordering, whether disabled/unpublished locales are included, and any permission requirement.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, but its brevity leaves room for a short usage clause that would cost little and add a lot.

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 zero-parameter read tool with no output schema, the description covers what is returned at a high level (locales plus public URLs). It stops short of noting auth requirements, whether the default locale is flagged, or how the URLs should be used, which leaves some ambiguity an agent may need to resolve by calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is no parameter semantics to explain. The description correctly implies the call is unfiltered and returns everything configured.

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 configured Knowledge Base locales') and goes further by noting the payload includes their public URLs. The resource is clearly distinct from the sibling list_* tools (pages, tree, inboxes, operators), though the description never explicitly contrasts itself with them.

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 when-to-use guidance, no prerequisites (e.g. admin/settings access), and no named alternative for the case where an agent actually wants page or tree content instead of locale metadata. The agent must infer that this is only for locale enumeration.

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