Skip to main content
Glama
sam-wilkie

Kommo Kiro MCP

by sam-wilkie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

send_chat_message

Sends an outgoing chat message to a customer in a lead's conversation; finds the lead's talk and posts the text, failing if none exists.

Instructions

Send an outgoing chat message to the customer in a lead's conversation. Finds a conversation (talk) whose entity is this lead and posts to it; fails with an error if the lead has none. The message is delivered externally and cannot be recalled by this server, and repeated calls send duplicates. Use add_note for internal notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesMessage text sent to the customer.
lead_idYesID of a lead that already has an active conversation. Get it from list_leads.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.5
    • changedOutput schema / description
      Previous value: -"Kommo response for the posted chat message, passed through unchanged."New value: +"Kommo response to POST /talks/{talk_id}/send_message, passed through unchanged."
    • removedOutput schema / properties / _embedded
      Removed value: -{
-  "additionalProperties": true,
-  "description": "Embedded messages.",
-  "properties": {},
-  "type": "object"
-}
    • removedOutput schema / properties / _total_items
      Removed value: -{
-  "description": "Number of messages created.",
-  "type": "integer"
-}
  2. Changed1 schema field changedv1.0.3
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Kommo response for the posted chat message, passed through unchanged.",
+  "properties": {
+    "_embedded": {
+      "additionalProperties": true,
+      "description": "Embedded messages.",
+      "properties": {},
+      "type": "object"
+    },
+    "_total_items": {
+      "description": "Number of messages created.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / lead_id / description
      Added value: +"ID of a lead that already has an active conversation. Get it from list_leads."
    • addedInput schema / properties / text / description
      Added value: +"Message text sent to the customer."
  4. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so duplication and external reach are partly structured data. The description still adds genuine value with 'cannot be recalled by this server' and the hard precondition that the lead has a conversation, but the duplicate/external claims restate the annotations rather than extend them.

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?

Three short sentences, front-loaded with the action, then the lookup behavior, then the delivery warning and the alternative. Nothing is redundant or padding.

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

Completeness5/5

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

An output schema exists so return values need no explanation. Failure conditions, irreversibility, duplicate risk, and the sibling alternative are all present, leaving nothing an agent needs in order to call this correctly.

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% and both parameters are self-documented (text and lead_id with sourcing guidance from list_leads). The description adds no format, length or escaping detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (send), resource (chat message) and target (the customer in a lead's conversation), and explicitly distinguishes itself from add_note for internal notes. An agent can separate this from the other lead tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternative tool (add_note) and the condition that selects it, plus the precondition that the lead must already have an active conversation and the failure mode if it doesn't. Both when-to-use and when-not-to-use are covered.

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

Deploy Server

Other Tools