Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_visitors_count

Retrieves the count of visitors currently active on a workspace's chatbox widget, excluding those typing or actively chatting.

Instructions

Returns the number of visitors currently active on the workspace's chatbox widget. This is not a count of visitors currently typing or actively chatting.

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

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?

With no annotations, the description carries the full burden. It does disclose a genuinely non-obvious behavioral trait, namely that typing/chatting users are excluded from the figure, which prevents a common misread. It says nothing about permissions, whether the value is live or cached, what happens on an empty workspace, or the return type.

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?

Two short sentences, front-loaded with the positive definition before the clarifying exclusion. No filler, and the second sentence explicitly earns its place by correcting a plausible misinterpretation.

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 counter with no output schema, the description covers what is counted and over what scope. It could reasonably add the return type (integer) and how the count relates to list_visitors, but nothing needed to invoke the tool is missing.

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 meaning for the description to add. Baseline for a no-parameter tool applies.

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 pair ('Returns the number of visitors') with scope constrained to the workspace's chatbox widget. It further narrows the metric by excluding typing/chatting visitors. It does not explicitly differentiate itself from list_visitors, which is the nearest sibling, so it falls short of a 5.

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?

Use is implied: call this when a scalar count is wanted rather than a visitor list. The description never names list_visitors or states any condition such as 'use the list tool when you need visitor identities'. No prerequisites or exclusions are given.

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