Skip to main content
Glama
Sign In
Kommo CRM MCP Server

Kommo CRM MCP Server

by E0DUAR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

kommo_create_note

Create notes for leads, contacts, or companies in Kommo CRM by specifying entity type, ID, and note text.

Instructions

Create a new note for an entity

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": {
      "entityType": "<entityType>",
      "entityId": "<entityId>",
      "text": "<text>"
    },
    "name": "kommo_create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityTypeYes
entityIdYes
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Create a new note' without mentioning side effects, idempotency, authentication needs, or the requirement that the target entity exists.

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?

The description is a single, short sentence. While concise, it omits essential information, making it minimally adequate but not optimally structured.

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

Completeness2/5

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

Given 3 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain return value, error behavior, or validation rules, and does not mention that the entity must already exist.

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

Parameters1/5

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

Schema coverage is 0% and the description adds no parameter meanings. 'entityType' enum values are unexplained, 'entityId' and 'text' lack guidance on format or constraints.

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 clearly states the verb 'Create' and resource 'note', and the 'for an entity' qualifier distinguishes it from other create tools (e.g., kommo_create_contact). However, 'entity' is vague; the supported types (leads, contacts, companies) are only revealed in 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 Guidelines2/5

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

No guidance on when to use this tool versus siblings like kommo_update_note or kommo_get_note. No mention of prerequisites (e.g., entity must exist) or scenarios where other tools are preferred.

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