Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

move_conversation_inbox

Moves a conversation to a specified inbox using session_id and inbox_id; discover valid inbox IDs with list_inboxes when needed.

Instructions

Moves a conversation to the specified inbox. Use the list_inboxes tool to discover a valid inbox_id when it is not already known.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "inbox_id": "<inbox_id>"
    },
    "name": "move_conversation_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
inbox_idYesThe identifier of the inbox to move the conversation to ('inbox_id' in the list of inboxes).
session_idYesThe conversation session identifier ('session_id' value).

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?

With no annotations present, the description carries the full behavioral burden, and it does not say whether the move replaces or appends to an existing inbox assignment, what permissions are required, whether it is reversible, or what the call returns. Only the destination-discovery hint adds value beyond the name.

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 short sentences with the core action front-loaded and the discovery hint placed after it; nothing is redundant. It is efficient, though the second sentence is the only element that earns its place beyond the first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description should disclose side effects, required permissions, and expected outcome, all of which are absent. An agent knows what to call but not what will change or what it will get back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with both session_id and inbox_id fully documented in the schema, so the baseline is 3. The description only reinforces that inbox_id must be a valid existing inbox and points at list_inboxes for discovery, adding no syntax or format detail beyond the schema.

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?

The description gives a specific verb and resource ("Moves a conversation to the specified inbox"), so an agent can immediately tell this is a reassignment operation on a conversation. It stops short of explicitly contrasting with siblings like change_conversation_state, but the action itself is unambiguous.

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?

It supplies one concrete usage hint — call list_inboxes to obtain a valid inbox_id when unknown — which is genuinely actionable. However, it offers no guidance on when this tool is appropriate versus related tools such as change_conversation_state, nor any preconditions for the move.

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