Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_inboxes

List a Crisp workspace's available sub-inboxes to see how conversations are grouped. Use it to identify inboxes before filtering or routing conversations.

Instructions

Lists the available workspace sub-inboxes, which group conversations together.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Lists' implies a non-mutating read and 'available' hints at a scoped, permission-filtered result set, but nothing is said about permissions, ordering, or result size. For a zero-parameter list tool the risk is low, so this is adequate rather than deficient.

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 front-loaded sentence with no filler, and the key noun 'sub-inboxes' appears immediately. The trailing relative clause is useful rather than redundant, though 'workspace sub-inboxes' could have been defined slightly more sharply.

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 output schema, the description is the only place the return shape can be described, and it gives just a one-line characterization ('sub-inboxes, which group conversations together') without saying what fields an inbox carries or whether ordering is stable. For a simple discovery tool this is minimally sufficient, but it leaves the agent guessing about the payload.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter schema applies. The description correctly avoids inventing arguments that do not exist.

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 ('Lists the available workspace sub-inboxes') and adds a conceptual gloss ('which group conversations together') that makes the object concrete. It does not explicitly contrast itself with siblings such as list_conversations_at_page or move_conversation_inbox, so it stops short of full differentiation.

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 when-to-use guidance, no preconditions, and no pointer to an alternative tool. The agent must infer from the name alone that this is the discovery step before calling move_conversation_inbox or filtering conversations.

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