Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

send_conversation_message_note

Add an internal note to an existing conversation that stays private to workspace operators and is not sent to the recipient.

Instructions

Adds an internal note to an existing conversation. Notes are visible only to workspace operators and are not sent to the recipient. They stay private to your team at any time.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text content for the note message to send in the conversation.
mentionsNoThe operator identifiers to mention and notify (identifiers are 'user_id' from the list of operators).
session_idYesThe conversation session identifier ('session_id' value).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/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 and does disclose the key trait: the note is visible only to workspace operators and never delivered to the recipient. It says nothing about permission requirements, mention-driven notifications, failure behavior on an invalid session, or whether the note appears in message listings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded with the action, but the third sentence ('They stay private to your team at any time') restates the visibility point already made and adds a vague 'at any time' claim rather than new information.

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

Completeness4/5

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

For a simple three-parameter mutation with no output schema and no annotations, the description covers purpose and the critical privacy/delivery semantics an agent needs before calling it. Remaining gaps around permissions and errors are minor for this complexity level.

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 text, session_id, and mentions are already fully documented, including the mention notification side effect. The description adds no additional meaning about parameter format or constraints beyond the schema baseline.

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+resource: 'Adds an internal note to an existing conversation.' The clause 'not sent to the recipient' implicitly distinguishes it from the sibling send_conversation_message_text, though it never names that alternative explicitly.

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 implied: use this for internal, operator-only commentary rather than customer-facing replies. There are no explicit when-not conditions, prerequisites, or named alternatives despite send_conversation_message_text existing in the sibling set.

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