Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_website_settings

Fetch a workspace's full settings to inspect configuration or locate a specific option. Use it when users ask about workspace setup or need setting details.

Instructions

Returns the workspace's full settings. This advanced response may be large; use it when the user asks about workspace 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_website_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute one useful trait: the response 'may be large,' which matters for context budgeting. It does not state read-only semantics explicitly, permission requirements, or whether the settings are cached/live, so the behavioral picture is only partially filled in.

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 sentences, front-loaded with the action and resource, then the usage condition and the size caveat. Nearly zero waste; the only weak spot is the vague phrase 'advanced response,' which is filler compared to the concrete size warning beside it.

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 zero-parameter read tool with no output schema and no annotations, the description says enough to call it correctly: what it returns, when to call it, and that the payload may be large. Missing only the read-only/permission framing and a sibling comparison, both minor given the tool's simplicity.

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 nothing for the description to disambiguate; the baseline of 4 applies. The description correctly avoids implying any filtering capability it does not have.

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: 'Returns the workspace's full settings,' which clearly tells an agent this is an unfiltered read of workspace configuration. It does not explicitly differentiate from the sibling get_helpdesk_settings, so the boundary between the two settings tools is left to inference.

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?

Gives an explicit trigger: 'use it when the user asks about workspace configuration or a specific setting,' and signals the response may be large, implying it should not be called speculatively. It lacks a stated alternative (e.g., when to prefer get_helpdesk_settings), so it stops short of full routing guidance.

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