Kommo CRM MCP Server

kommo_create_task

Create a new task in Kommo CRM with a due date and link it to a lead, contact, or company.

Instructions

Create a new task

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": {
      "text": "<text>",
      "complete_till": "<complete_till>",
      "entity_id": "<entity_id>",
      "entity_type": "<entity_type>"
    },
    "name": "kommo_create_task"
  }
}

Input Schema

Name	Required	Description
`text`	Yes
`complete_till`	Yes	Unix timestamp
`entity_id`	Yes
`entity_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 13, 2026

TDQS

C2.2/5.0

Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only states 'Create a new task' without any details on side effects, permissions required, or whether it mutates state. The agent cannot assess safety or prerequisites.

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 sentence, which is concise. However, it sacrifices necessary detail for brevity; it could be slightly longer to improve clarity without being verbose.

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 the tool has 4 required parameters and no output schema, the description is incomplete. It does not explain the purpose of the task, its association with entities, or return value. The context signals indicate low coverage, leaving gaps.

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 description coverage is only 25% (only 'complete_till' has a description). The tool description adds zero additional information about parameters like 'text', 'entity_id', or 'entity_type'. It fails to compensate for the schema's lack of documentation.

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

Purpose3/5

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

The description 'Create a new task' clearly indicates it creates a task resource, which is appropriate for a create tool. However, it does not distinguish this tool from sibling create tools like kommo_create_note or kommo_create_contact, as the description is too generic.

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 is provided on when to use this tool versus alternatives. For example, it does not explain how tasks differ from notes or other entities, leaving the agent without context for selection.

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

Deploy Server