Fetch the Salesbots configured for a Kommo account using its client slug. Supports pagination through page and limit parameters.
Busca a lista de Salesbots configurados na conta Kommo.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| limit | No | ||
| client_slug | Yes | Identificador do cliente (slug) |
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 of behavioral disclosure. It only states that it fetches a list of Salesbots and gives no information about pagination behavior, read-only safety, authentication needs, or possible error conditions.
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 clear sentence with no filler. The verb and resource are front-loaded, and every word contributes to the basic purpose.
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 tool with no output schema, no annotations, and only 33% schema parameter coverage, the description is too thin. It does not mention pagination defaults, the required client_slug usage, or how this tool relates to get_salesbot_by_id, leaving an agent without enough context to invoke it with confidence.
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?
Schema description coverage is only 33%, and the description adds no parameter-level meaning. It does not explain page, limit, or how client_slug relates to the account context beyond what the schema already states, so it fails to compensate for the large documentation gap.
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 uses a specific verb ('Busca') and resource ('lista de Salesbots') and conveys that this tool fetches the collection of Salesbots for the Kommo account. It is clearly a list operation and is distinguishable from the singular get_salesbot_by_id sibling, though it does not explicitly contrast itself with that sibling.
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?
The description gives no guidance on when to use this tool versus alternatives like get_salesbot_by_id, launch_salesbot, or stop_salesbot. A listing use case is implied, but there are no exclusions, alternatives, or contextual conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.