Clientes (módulo de vendas recorrentes/RFM do Kommo). action: list | get | create | update. Requer o módulo de clientes ativo na conta.
[Flattened action: list]
Bulk support: accepts ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| ids | No | ||
| data | No | ||
| page | No | ||
| with | No | ||
| limit | No | ||
| order | No | ||
| query | No | ||
| filter | No | ||
| account | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are all false, so the description must convey behavioral traits. It states the module requirement and bulk support, but does not clarify read-only nature, side effects, or data output. The multi-action mention further obscures whether this is purely a read operation or also supports writes.
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 short, but the structure is confusing: it starts with a generic module name, lists multiple actions, then clarifies 'Flattened action: list'. It could be more direct and front-loaded with the intended action. Not verbose, but lacks logical flow.
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?
The tool is a list operation with many parameters and no output schema, yet the description is extremely sparse. It omits pagination, filtering, ordering, query syntax, response format, and any operational details beyond a vague bulk-support statement. Inadequate for correct invocation.
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?
There are 10 parameters and schema description coverage is 0%. The description does not explain any parameter except indirectly mentioning 'ids' for bulk support. It provides no meaning for 'data', 'page', 'with', 'limit', 'order', 'query', 'filter', or 'account', leaving agents completely unaided.
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 tool name 'kommo_customers_list' and the description's 'Clientes' and 'Flattened action: list' clearly indicate it is for listing customers. However, the mention of 'action: list | get | create | update' before the flattened action introduces ambiguity about which action is actually executed, reducing clarity.
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?
No guidance is given on when to use this tool versus siblings like kommo_customers_get or kommo_customers_update. The only hint is the prerequisite of the customer module being active, but there is no when-to-use or when-not-to-use advice, nor any mention of alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.