Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_operators_active

Lists workspace operators who are currently active in a Crisp app, helping you check who is online or available for support.

Instructions

Lists workspace operators who are currently active in a Crisp app.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/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 behavioral burden. It implies a read-only listing but never defines what "active" means (online now, recently connected, enabled account), nor does it mention pagination, result ordering, or return shape for what could be a large operator set.

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 sentence with no padding, and the resource plus scope qualifier are front-loaded. Nothing is wasted, though the terseness comes at the cost of the definitional detail noted above.

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 adequate. The unresolved ambiguity about what "active" measures and how results relate to list_operators leaves a real gap an agent could stumble on when choosing between the two.

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 the baseline is 4; there is nothing for the description to disambiguate. Schema coverage is 100% and the empty object schema is unambiguous on its own.

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 (workspace operators) with an added scope qualifier ("currently active"), so the agent knows this is a filtered subset rather than all operators. It does not name or contrast with the sibling list_operators, so the distinction between the two must be inferred from the word "active".

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 explicit when-to-use guidance, no statement of when not to use it, and no reference to list_operators as the alternative for the unfiltered case. The name and "active" qualifier imply a use case, but nothing in the description confirms or excludes one.

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