Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_helpdesk_information

Retrieve basic Knowledge Base details, including its name and URL, to identify the helpdesk quickly.

Instructions

Returns basic Knowledge Base information, including its name and URL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It does convey the return contents (name and URL) and the word "Returns" implies a non-mutating read, but it says nothing about permissions, errors, or what "basic" omits; for a zero-parameter read this is adequate rather than rich.

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?

A single front-loaded sentence with no filler or redundancy. It could be marginally stronger by stating what distinguishes the returned data from the settings tools, but nothing needs to be cut.

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 no-parameter read with no output schema, the description does the essential job of naming the returned fields. The hedge "basic ... including" leaves some ambiguity about whether additional fields appear, which matters because there is no output schema to confirm the shape.

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 schema has zero properties, so there are no parameter semantics to explain and the baseline of 4 applies. The description correctly requires no arguments and adds no misleading input expectations.

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 gives a specific verb and resource ("Returns basic Knowledge Base information") and names two concrete fields, its name and URL. It is clear what the tool does, but it does not distinguish itself from nearby siblings such as get_helpdesk_settings or get_website_information, so an agent must infer the boundary.

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 exclusions, and no mention of an alternative tool. The only clue is the word "basic," which weakly implies this is the lightweight option compared to settings-specific tools, but nothing states that.

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