Skip to main content
Glama
amocrm-kommo-mcp

amocrm-kommo-mcp

Зависшие сделки

crm_stale_leads
Read-onlyIdempotent

Find open deals at risk: no updates for N+ days, no planned task or overdue task. Returns stale leads sorted by value for daily funnel review and manager reminders.

Instructions

Открытые сделки под риском: без изменений days+ дней, без запланированной задачи или с просроченной задачей. Возвращает count, at_risk_budget и leads (id, name, price, stage, pipeline, responsible, idle_days, reasons), сначала самые дорогие. Используйте для «что зависло», ежедневной ревизии воронки и напоминаний менеджерам; общая картина — crm_pipeline_report, задачи — crm_tasks. Смотрит до 3000 открытых сделок. Требует AMOCRM_DOMAIN и AMOCRM_TOKEN; лимит amoCRM 7 запросов/с соблюдается автоматически. Только чтение.

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": "crm_stale_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoСколько дней без изменений считать зависанием
limitNoМаксимум сделок в ответе
pipeline_idNoID воронки (из crm_account)
include_no_taskNoДобавить свежие сделки без запланированной задачи
responsible_user_idNoID ответственного менеджера (из crm_account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.2
    • addedInput schema / properties / limit / description
      Added value: +"Максимум сделок в ответе"
    • addedInput schema / properties / pipeline_id / description
      Added value: +"ID воронки (из crm_account)"
    • addedInput schema / properties / responsible_user_id / description
      Added value: +"ID ответственного менеджера (из crm_account)"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: it scans up to 3000 open deals, requires AMOCRM_DOMAIN and AMOCRM_TOKEN, and self-throttles to amoCRM's 7 req/s limit. The only gap is no mention of what happens when the 3000-deal cap truncates results.

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?

Front-loaded with the at-risk definition and return shape, then routing, then operational limits. Dense and information-rich, though the single block could be broken up slightly for scanability.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating returned fields (count, at_risk_budget, leads with id, name, price, stage, pipeline, responsible, idle_days, reasons). Auth requirements, scan cap and rate-limit behavior are all covered, so an agent has enough to call it correctly.

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 every parameter is already documented, including days, limit, pipeline_id, include_no_task and responsible_user_id. The description reinforces the days threshold and result ordering, but adds no syntax or format detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (returns at-risk open deals) and precisely defines the inclusion criteria: unchanged for days+, and either no scheduled task or an overdue task. It also names the fields returned and the ordering, so an agent knows exactly what it gets.

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

Usage Guidelines5/5

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

Explicitly states when to use it ('что зависло', daily funnel review, manager reminders) and routes to named alternatives: crm_pipeline_report for the overall picture and crm_tasks for tasks. No inference required.

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