Skip to main content
Glama
E0DUAR

Kommo CRM MCP Server

by E0DUAR

kommo_create_contact

Create a new contact record in Kommo CRM with required name and optional details like first name, last name, and responsible user.

Instructions

Create a new contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesContact name
first_nameNo
last_nameNo
responsible_user_idNo
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as whether existing contacts are checked, required permissions, or side effects. Minimal information.

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 short and direct, but at the expense of necessary detail. It is not verbose but fails to include essential context.

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 4 parameters, no output schema, and no annotations, the description is insufficient. Missing details about optional fields, return values, and typical usage scenarios.

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

Parameters2/5

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

Schema coverage is low (25%), with only 'name' having a description. The tool description adds no additional parameter meaning, leaving other fields unexplained.

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 'Create a new contact' clearly states the action and resource, but lacks differentiation from sibling tools that create other entities. It is specific enough for a basic understanding.

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 alternatives like update or search. The description does not mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/E0DUAR/kommo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server