Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

leads

Manage KeyCRM pipeline cards: list, retrieve, create, update, move between statuses, view kanban boards, add products, and convert cards into orders.

Instructions

Pipeline cards (лиды / сделки / заявки).

actions: list - cards with pagination; filters go through the official API ({"status_id": 1, "pipeline_id": 1, "created_between": ["...","..."]}) get - full card (contact, source, products, payments) create - required: status_id, communicate_at, currency_code optional: title, pipeline_id, source_id, manager_id, contact{...} update - PUT /leads/{id} with a partial body move - set status_id (moves between pipelines too) pipelines - list of pipelines with their statuses desk - kanban board: statuses grouped with cards complete - convert card into an order (PUT /leads/{id}/order) add_product / copy remove - BLOCKED on purpose: the batch endpoint removes whole status columns when ids do not match exactly. Delete cards in the UI.

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

Input Schema

NameRequiredDescriptionDefault
idsNo
dataNo
pageNo
limitNo
actionNolist
filtersNo
includeNo
lead_idNo
status_idNo
pipeline_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses required create fields, that update is a PUT with a partial body, that move can shift a card between pipelines, that complete hits PUT /leads/{id}/order, and that remove is deliberately disabled because the batch endpoint deletes whole status columns. Missing are permission/auth requirements, whether create/update are reversible, and side effects on related objects.

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 resource line followed by a terse per-action list with no filler; each entry maps action to effect. A couple of entries are too compressed to be actionable ('add_product / copy' has no explanation), which is the only structural weakness.

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 10-parameter multi-action mutation tool with no annotations but an output schema, the description covers the action space, required inputs, and the one dangerous action. Remaining gaps — pagination defaults for page/limit, auth prerequisites, and defaults for the 'action' parameter — are modest given the output schema handles return shapes.

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 0% with 10 generic parameters (ids, data, filters, include, action), so the description must compensate, and it largely does: it shows the filter object shape with example keys, lists the required create body fields, and explains that update takes a partial body and move takes status_id. It still leaves the roles of 'ids', 'include', and how 'data' vs 'filters' differ across actions unstated.

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 opens with a specific resource identification ('Pipeline cards (лиды / сделки / заявки)') and then enumerates concrete operations (list, get, create, update, move, complete), so an agent can tell this is the CRM lead/deal-card endpoint. It does not distinguish itself from siblings by name, but the resource scope is narrow enough that no ambiguity arises.

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

Usage Guidelines4/5

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

The action roster effectively acts as a routing table: use 'list' with filters, 'get' for a full card, 'move' to change status including across pipelines, 'complete' to convert to an order. It also gives an explicit prohibition ('remove - BLOCKED on purpose ... Delete cards in the UI'), which is stronger than most definitions provide. It stops short of stating when to prefer this tool over siblings such as orders or clients.

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