Kommo Kiro MCP

Overview Schema Source Related Servers Discussions Admin

list_chat_templates

Read-onlyIdempotent

Retrieve the account's chat message templates from Kommo. Read-only; returns template objects for review or selection without sending messages.

Instructions

List the account's chat message templates. Read-only. Returns template objects as provided by Kommo. This server cannot send a template; it only lists them (send_chat_message sends plain text).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	Returned entities.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.3Oct 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Chat templates, as {items: [...]}.",
+  "properties": {
+    "items": {
+      "description": "Returned entities.",
+      "items": {
+        "additionalProperties": true,
+        "description": "A chat message template.",
+        "properties": {
+          "content": {
+            "description": "Template text.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Template ID.",
+            "type": "integer"
+          },
+          "name": {
+            "description": "Template name.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Approval status.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Channel type.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedv1.0.0Oct 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuine value beyond them: it states templates are returned 'as provided by Kommo' and that the server is list-only with no send capability, which the annotations do not convey.

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, each front-loaded and purposeful: purpose, safety/return, and the send limitation. Nothing is redundant and the most important information (what it does) leads.

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?

With an output schema present, return shape need not be explained, and rich annotations cover the safety profile. The description supplies the one thing structure cannot: the inability to send templates, making the definition complete for a zero-param list tool.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and no parameter semantics to add. Baseline 4 for a param-less tool is appropriate.

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?

States a specific verb (List) and resource (the account's chat message templates), so the agent knows exactly what the tool returns. It also distinguishes itself from the sibling send_chat_message by clarifying it only lists and cannot send, removing ambiguity with the closest related tool.

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

Usage Guidelines4/5

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

The description gives clear scope: use this to list templates, and it explicitly notes the server cannot send a template while pointing at send_chat_message (clarifying that tool sends plain text only). This is strong routing context, though it stops short of explicit when/when-not triggers since there is no sibling template tool to disambiguate against.

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