Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

send_conversation_message_text

Sends a customer-visible text message to a recipient in an existing conversation using the session ID and message text.

Instructions

Sends a customer-visible text message to the recipient in an existing conversation.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text content for the text message to send in the conversation.
session_idYesThe conversation session identifier ('session_id' value).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/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 usefully discloses the two most important behavioral facts — the message is customer-visible and the conversation must already exist — but says nothing about permissions, delivery guarantees, rate limits, or side effects of an irreversible customer-facing send.

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?

A single front-loaded sentence with no filler. The scope constraint ("customer-visible", "existing conversation") appears before the object, so an agent skimming gets the key distinction immediately.

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 simple two-parameter send with no annotations and no output schema, the description covers what it does and the prerequisite but leaves return behavior and error conditions unaddressed. Adequate to invoke, but thin for a customer-facing mutation.

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%, so both parameters are already documented in the schema. The description adds no meaning beyond "text" and "conversation" — no length limits, formatting rules, or constraints on what session_id must reference. The baseline of 3 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?

"Sends a customer-visible text message ... in an existing conversation" gives a specific verb, resource and scope. The qualifier "customer-visible" implicitly separates it from the note-sending sibling without naming it, so the agent can infer the distinction, though a direct sibling reference would remove any ambiguity.

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?

Usage is only implied: "in an existing conversation" signals the prerequisite that a session must already exist, but the description never states when to pick this over send_conversation_message_note or other conversation tools, nor any exclusions.

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