Add a new contact to a Kommo CRM client account by providing first name and client slug. Supports custom fields for extended contact data.
Cria um novo contato no Kommo CRM.
| Name | Required | Description | Default |
|---|---|---|---|
| last_name | No | Sobrenome | |
| first_name | Yes | Primeiro nome do contato | |
| client_slug | Yes | Identificador do cliente (slug) | |
| custom_fields_values | No | Array de campos customizados |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses only the core mutation—creating a contact—but not return value, idempotency, required permissions, duplicate behavior, or error handling. This is minimal behavioral disclosure for a write operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It is efficiently concise, though it offers very little beyond the basic action and target system.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple create operation with fully described parameters, the description is minimally adequate. However, with no output schema and no annotations, it lacks return-value expectations and any usage context, which could leave an agent uncertain about how to confirm success or handle the created contact.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with all four parameters already described. The tool description adds no parameter-level detail beyond what the schema provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action and resource: 'Cria um novo contato no Kommo CRM' (Creates a new contact in Kommo CRM). This distinguishes it from siblings such as get_contacts, update_contact, and create_lead.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives like update_contact or create_lead. No exclusions, prerequisites, or context are provided, leaving the agent to infer usage solely from the generic description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.