Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

clients

Manage KeyCRM buyers: list, search, create, update and delete clients, sync phone and email profiles, and view order history or pipeline leads.

Instructions

Buyers / clients (покупці).

IMPORTANT: POST /clients ignores phone and email. Contacts live in separate profiles: POST /clients/{id}/profiles {"client_id", "field": "phone"|"email", "value"}. create() accepts phone/email and writes the profiles right after the client, update() does the same when phone/email are passed.

actions: list - paginated clients with meta get - full client (phones, emails, profile list, shipping addresses) create - data{full_name, note, manager_id, ...} plus optional phone/email update - data{...} plus optional phone/email delete - DELETE /clients/{id} search - by name/phone/email set_profile - client_id + field ("phone"/"email"/custom) + value orders - order history of the client leads - pipeline cards of the client

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

Input Schema

NameRequiredDescriptionDefault
dataNo
pageNo
emailNo
fieldNo
limitNo
phoneNo
valueNo
actionNolist
searchNo
client_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely non-obvious behavior: POST /clients ignores phone and email because contacts live in separate profiles, and create()/update() compensate by writing profiles afterward. However, it says nothing about destructive delete semantics, required permissions, or pagination/meta behavior, leaving significant behavioral gaps for a multi-action write-capable tool.

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-loads the critical profile caveat, then a compact action table with one line each. Dense and scannable with minimal waste; only minor redundancy between the IMPORTANT block and the create/update lines.

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, zero-schema-coverage, unannotated tool, the description covers the hardest parts: the action vocabulary and the phone/email profile indirection. Remaining gaps are the mapping of page/limit/search params to specific actions and any statement about what delete or list returns (partly mitigated by an existing output schema).

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 description coverage is 0% and the action enum is not defined in the schema, so the description does real work: it supplies the valid action values, explains data{full_name, note, manager_id, ...} for create/update, defines client_id + field ('phone'/'email'/custom) + value for set_profile, and indicates search matches name/phone/email. Page/limit defaults and the standalone 'search' vs 'search' action relationship remain unclarified.

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 names the resource (buyers/clients) and enumerates the concrete actions it exposes (list, get, create, update, delete, search, set_profile, orders, leads), so an agent knows this is the client CRUD hub rather than the lead/order tooling. It does not explicitly contrast itself with sibling tools like leads or orders, but the action set makes the scope clear.

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?

Each action carries a short inline purpose (e.g. 'orders - order history of the client', 'leads - pipeline cards of the client'), which effectively tells an agent which action to pick for a given intent. It also signals that create/update accept phone/email while set_profile is the dedicated path. There are no explicit exclusions or cross-tool alternatives, keeping it at 4 rather than 5.

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