Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

status_transitions

Count unique leads entering each status, from-to stage moves, and moves per user over a period to analyze pipeline conversion and manager activity.

Instructions

Count stage moves over a period from the event log: how many unique leads entered each status, from→to transition counts, and moves per user. Use for conversion between stages and manager activity.

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": {
      "created_from": "<created_from>"
    },
    "name": "status_transitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_pagesNoSafety cap on pages of 100 events (default 60 = 6,000 moves)
created_byNoOnly moves made by these user IDs
created_toNoPeriod end (default: now)
pipeline_idNoOnly moves that end in this pipeline
created_fromYesPeriod start
status_afterNoOnly moves INTO these statuses
include_lead_idsNoInclude lead IDs per target status (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the numbers come from scanning the event log and are aggregated (unique leads, transition pairs, per-user counts), which implies a read-only but potentially expensive operation, yet it never states read-only semantics, cost, or truncation behavior beyond the schema's max_pages cap.

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?

Two sentences, front-loaded with the core action and the three metrics, followed by a single usage sentence. Every clause maps to a distinct output dimension; nothing is redundant.

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?

With no output schema, the description correctly compensates by enumerating the return shape, which is the most valuable thing it could add for a 7-parameter aggregation tool. Remaining gaps are minor: pagination/truncation behavior and what include_lead_ids changes are left entirely to the schema.

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 the schema already documents every parameter including defaults and caps. The description's output framing ("unique leads entered each status", "moves per user") hints at what status_after and created_by drive, but adds no syntax or filtering semantics 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?

States a specific verb (count) and resource (stage moves from the event log) and enumerates the three things returned: unique leads entering each status, from→to transition counts, and moves per user. That is far more precise than the sibling list_events, though no sibling is named to make the boundary explicit.

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 for conversion between stages and manager activity" gives an implied usage context but no when-not conditions and no named alternative (e.g. list_events for raw event rows). An agent can infer the fit but must still decide on its own.

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