Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

get_lead_full

Retrieve a complete deal card for one lead, including fields, stage, responsible person, company, contacts, notes, tasks, stage history, and configured Telegram/MAX messages to analyze the deal.

Instructions

One-call deal card: lead fields with stage and responsible names, company, contacts with phones/emails, notes (comments, calls), tasks, stage history, and the Telegram/MAX correspondence from Chatsky when configured. Use this to analyze a single deal.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lead_id": "<lead_id>"
    },
    "name": "get_lead_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYesLead ID
notes_limitNoMax notes to return, newest first (default 50)
messages_limitNoMax messenger messages from Chatsky (default 100)
include_field_historyNoAlso include custom-field change events in the history (default false: stages, responsible, tags only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose the returned payload surface and the important conditional 'when configured' qualifier on Chatsky correspondence, which is genuinely useful. It omits that this is a read-only heavy aggregation call, any permission/auth requirements, and any sense of response size or cost given up to 750 combined notes/messages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the payload inventory before the usage sentence. Dense but readable, with no filler. Minor cost is that the long comma-separated inventory is slightly hard to scan, but every item listed is content the caller receives.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read aggregator with no output schema and no annotations, the description covers the return surface well enough to decide whether to call it. The remaining gap is behavioral rather than structural: nothing warns that this is an expensive multi-entity fetch whose limits should be tuned.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters are already documented with defaults and maximums, which sets the baseline at 3. The description's mention of notes, Chatsky messages, and stage history loosely maps to notes_limit, messages_limit, and include_field_history but adds no format, ordering, or default information beyond the schema.

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 uses a concrete framing ('One-call deal card') and enumerates exactly what the tool returns: lead fields with stage and responsible names, company, contacts with phones/emails, notes, tasks, stage history, and messenger correspondence. This is far more specific than a name restatement. It stops short of 5 because it never names the sibling get_lead or states how this aggregate differs from that lighter tool.

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?

'Use this to analyze a single deal' gives a real but narrow usage cue. There is no when-not guidance, no mention of the cheaper get_lead alternative for simple lookups, and no note that this is a heavyweight aggregate call best avoided in bulk loops. The condition for choosing this over siblings is implied rather than stated.

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