Skip to main content
Glama

kommo_talks_get

Read-onlyIdempotent

Conversas (talks) do inbox unificado. action: list (filtrável por contact_id/entity_id/only_in_work via filter JSON) | get (por id). Para ler o texto das mensagens, use kommo_talks_messages.

[Flattened action: get]

Bulk support: accepts ids for batched execution.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kommo_talks_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
idsNo
pageNo
limitNo
filterNo
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the bulk-ids behavior and the pointer to kommo_talks_messages. It says nothing about what a talk record contains or how results are shaped for batched ids.

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 text is short and the routing hint is placed early enough to be useful. But sentences describing the list action and the '[Flattened action: get]' marker are internal artifacts that do not help an agent invoke this specific tool.

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?

With six parameters, zero schema description coverage, and no output schema, the description should carry the load and does not. Pagination (page/limit), account scoping, and the return shape of a bulk-ids call are all unaddressed, leaving real gaps for correct invocation.

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 description coverage is 0% across six parameters, so the description must compensate and largely does not. It explains id/ids and mentions filter JSON, but page, limit, and account are undocumented in both schema and description. The filter details are also attached to the list action, not clearly to this tool.

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 identifies the resource (unified-inbox talks) and states get-by-id, which is what the flattened action actually does. However, it also describes a 'list' action with a filter JSON and points to a sibling kommo_talks_list existing separately, so an agent reading it cannot tell whether this tool also lists. The core purpose is understandable but muddied by leftover action text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one explicit routing rule: use kommo_talks_messages to read message text, which is genuinely useful. It also notes bulk execution via ids. It does not say when to use this versus kommo_talks_list, nor any pagination or scope guidance, leaving the main alternative unexplained.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.