Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_visitors

Retrieve visitors currently active on a workspace’s Crisp chatbox widget to identify live website traffic and support real-time engagement.

Instructions

Lists visitors currently active on the workspace's chatbox widget.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and mostly falls short. It does not say whether 'active' means currently online, how many visitors are returned, whether results are ordered or paginated, or what happens on a workspace with no widget.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundant restatement of the tool name. Every clause contributes scope information.

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?

With no annotations and no output schema, the description is the sole source of behavioral context, yet it says nothing about the shape of a returned visitor or result size. It is adequate to identify the tool but thin for an agent that must decide how to consume the response.

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 and the schema cannot be enriched further. Baseline 4 applies for a no-parameter tool.

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 ('Lists') and resource ('visitors') plus a narrowing scope ('currently active on the workspace's chatbox widget'), so the agent knows precisely what comes back. It does not distinguish itself from the similar sibling get_visitors_count, leaving the agent to infer that this returns records while that one returns a tally.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the 'currently active' scoping, which suggests on-the-spot monitoring rather than historical listing. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as get_visitors_count or list_operators_active.

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