Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

change_conversation_state

Set a Crisp conversation to resolved, unresolved, or pending by session ID to reflect its current support status.

Instructions

Changes a conversation's state to resolved, unresolved, or pending.

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>"
    },
    "name": "change_conversation_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoThe new state for the conversation.resolved
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?

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation mutates state and names the allowed values, but it does not state permission requirements, reversibility, side effects, idempotency, or what the response contains.

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?

The definition is a single front-loaded sentence with no filler or unnecessary wording. It is appropriately sized for a simple mutation tool.

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 two-parameter tool with a fully described schema and no output schema, the definition is enough to invoke the tool correctly. However, it leaves behavioral gaps around permissions, side effects, and return behavior that are especially relevant for a mutation tool with no annotations.

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 description coverage is 100%, so both parameters are already documented in the schema, including the state enum and default. The description repeats the enum values but adds no syntax, constraints, or meaning beyond what the schema provides.

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 states a specific verb ('Changes'), resource ('conversation's state'), and valid target states (resolved, unresolved, pending). It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as move_conversation_inbox or the set_conversation_* tools.

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?

The definition gives no when-to-use guidance, no exclusions, and no alternatives. An agent can infer that this tool is for state changes, but nothing explains when to prefer it over related conversation-mutation tools.

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