Skip to main content
Glama
amocrm-kommo-mcp

amocrm-kommo-mcp

Отчёт по воронке продаж

crm_pipeline_report
Read-onlyIdempotent

Analyze one sales pipeline for deals created in a period (default 30 days): stage budgets, win/loss/open, win rate, avg deal, cycle time, and manager ranking by won revenue.

Instructions

Аналитика отдела продаж по одной воронке для сделок, созданных за период (по умолчанию 30 дней): stages (сделки и бюджет по этапам), won/lost/open, win_rate_pct (успешные / закрытые), avg_deal, avg_cycle_days (от создания до успеха) и managers — рейтинг менеджеров по выигранному бюджету. Используйте для «как идут продажи», «кто лучше закрывает», сравнения месяцев; конкретные сделки ищите crm_search_leads, проблемные — crm_stale_leads. Загружает до max_leads сделок (truncated=true, если упёрлись), на больших периодах может занять десятки секунд. Требует 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_pipeline_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_leadsNoСколько сделок максимум загрузить для расчёта
created_toNoКонец периода (по умолчанию сейчас)
pipeline_idNoВоронка; по умолчанию основная
created_fromNoНачало периода (по умолчанию 30 дней назад)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • changedInput schema / properties / created_to / description
      Previous value: -"Дата ГГГГ-ММ-ДД или дата-время ISO"New value: +"Конец периода (по умолчанию сейчас)"
    • addedInput schema / properties / max_leads / description
      Added value: +"Сколько сделок максимум загрузить для расчёта"
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the truncation contract (loads up to max_leads, truncated=true when hit), latency risk on large periods ('занять десятки секунд'), required env vars AMOCRM_DOMAIN/AMOCRM_TOKEN, and that the 7 req/s amoCRM limit is handled automatically. This is exactly the operational context annotations cannot carry.

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

Conciseness5/5

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

Single dense paragraph but strictly front-loaded: purpose and output fields first, usage and alternatives next, operational caveats last. Every clause carries distinct information with no filler.

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?

No output schema exists, yet the description enumerates the return payload fields so an agent knows what it will receive, and it covers the safety, auth, rate-limit and truncation dimensions needed to invoke and interpret a 4-param analytics tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: max_leads is tied to the truncated flag, and the period semantics (default 30 days) are framed as a window over lead creation dates, which clarifies created_from/created_to intent. Pipeline defaulting to the primary funnel is also restated usefully.

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?

Names a specific resource (sales analytics over one pipeline for leads created in a period) and enumerates the exact result fields (stages, won/lost/open, win_rate_pct, avg_deal, avg_cycle_days, managers ranking). An agent can distinguish it from crm_search_leads and crm_stale_leads, which the description explicitly points to for other needs.

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?

Explicit when-to-use triggers ('как идут продажи', 'кто лучше закрывает', comparing months) plus named alternatives with their selecting condition: crm_search_leads for concrete deals, crm_stale_leads for problematic ones. Nothing is left to inference.

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