Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_helpdesk_settings

Fetch Knowledge Base settings to answer questions about helpdesk configuration or inspect a specific setting. Returns detailed configuration data when needed.

Instructions

Returns the Knowledge Base settings. This advanced response may be large; use it when the user asks about Knowledge Base configuration or a specific setting.

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": "get_helpdesk_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/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 burden. It discloses one useful trait, that the response can be large and should be used deliberately, and 'Returns' implies a read-only operation. It says nothing about permissions, error behavior, or the shape of the settings payload.

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?

Two short sentences that are front-loaded with the resource and then the usage condition; nothing is wasted. The phrase 'advanced response' is slightly vague, but the size warning earns its place.

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 when to call it but not what the settings contain or how they are structured. Because no output schema exists, an agent has no other source for the return shape, which leaves a real gap.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing filtering options.

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?

The description names a specific verb ('Returns') and resource ('Knowledge Base settings'), which is clear on its own. It does not explicitly differentiate itself from the sibling get_website_settings or get_helpdesk_information, and the resource label ('Knowledge Base') differs from the tool name ('helpdesk'), leaving a small ambiguity about scope.

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 an explicit selection condition: use it when the user asks about Knowledge Base configuration or a specific setting. It also warns that the response may be large, which implicitly discourages casual calls. There are no stated exclusions or named alternatives, so it stops 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.