Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

conversations

Manage KeyCRM chats by listing threads, reading messages, checking unread items, and sending replies to keep customer communication organized.

Instructions

Chats (переписки): list, get, messages, unread, send (reply into a chat).

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

Input Schema

NameRequiredDescriptionDefault
dataNo
pageNo
limitNo
actionNolist
conversation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only hints that send writes ("reply into a chat"). It says nothing about permissions, side effects of sending, rate limits, or what unread/read semantics are.

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

Conciseness3/5

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

One short, front-loaded line with no filler, but it is terse to the point of under-specification, and the parenthetical Russian gloss adds little for an English-context agent.

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

Completeness2/5

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

A five-parameter tool with no annotations and zero schema coverage needs per-action parameter requirements and pagination behavior explained; the description provides neither. The output schema covers return values, so that omission is acceptable.

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 0%, so the description must compensate. It does supply the effective values of the action parameter (list, get, messages, unread, send), which the schema lacks as an enum, but it never explains conversation_id, page, limit, or the data payload.

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?

Names the resource (chats/переписки) and enumerates the concrete operations it multiplexes: list, get, messages, unread, send (reply). That is a specific verb set for a polymorphic tool, though it gives no differentiation from siblings such as comments or publications.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, and no indication of which action to choose or what each action requires. An agent must infer all routing decisions from the bare action names.

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