Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_website_information

Fetch basic details for the current Crisp workspace so MCP clients can identify and operate within the configured environment.

Instructions

Returns basic information for the current Crisp workspace.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and "Returns" only weakly implies a read-only operation. It does not disclose what fields constitute "basic information", whether it requires an authenticated workspace context, or how it behaves if the workspace is unconfigured.

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 short sentence with no filler or redundancy, and the core claim is front-loaded. It is perhaps too terse rather than bloated, which is not a conciseness problem.

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 is minimally viable but leaves the return contents and its distinction from get_website_settings unstated. Since no output schema exists, a sentence naming what "basic information" covers would materially improve 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 and the schema is an empty object, so there is no parameter meaning to convey. Baseline 4 applies; nothing in the description misleads about inputs.

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

Purpose3/5

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

"Returns basic information" gives a verb and a resource, but "basic information" is undefined and the description says "current Crisp workspace" while the tool is named get_website_information, leaving a name/description mismatch. Siblings like get_website_settings and get_helpdesk_information make the boundary between "website information" and "website settings" something the agent must guess.

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?

No when-to-use guidance is given: nothing says when this should be called instead of get_website_settings or get_helpdesk_information. The agent has to infer purpose purely from the tool name.

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