Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

crm_snapshot

Create a local JSON backup of KeyCRM account data before risky write operations, including pipeline cards, orders, clients, products, users, sources, statuses, and settings for recovery.

Instructions

Save a local JSON snapshot of the account before any risky operation.

Dumps pipeline cards (with contacts), orders, products, clients, users, sources, statuses and settings into keycrm-mcp/backups/.json. Use it before experiments with write endpoints: this is how the 26 lost cards were recovered on 01.11.2026.

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_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNo

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 provided, the description carries the full disclosure burden and does reasonably well: it states the local write side effect, the exact output path pattern (keycrm-mcp/backups/<timestamp>.json), and the data scope. It omits practical traits such as snapshot size, duration, and whether reads require credentials or elevated permissions, which keeps it short of a 5.

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?

The description is front-loaded with the action, then the data scope, then the when-to-use rationale. The anecdote about recovering 26 lost cards is longer than strictly necessary but does earn its place by motivating the pre-write snapshot habit.

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?

An output schema exists, so return values do not need explanation, and the description covers the write side effect and data contents well. The one real gap is the undocumented 'folder' parameter, which is the only thing an agent needs to set non-default.

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

Parameters2/5

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

Schema coverage is 0% for the single 'folder' parameter, and the description never explains what that parameter does, what it is relative to, or how it interacts with the default backups path. The mention of 'keycrm-mcp/backups/<timestamp>.json' only loosely hints at the default location, which is not enough to compensate for the coverage gap.

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?

The description names a specific verb and object ('Save a local JSON snapshot of the account') and enumerates exactly what is captured: pipeline cards with contacts, orders, products, clients, users, sources, statuses and settings. No sibling tool in the list performs backups, so there is no ambiguity about which tool to pick.

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?

It gives an explicit trigger condition: 'Use it before experiments with write endpoints' and 'before any risky operation'. There is no when-not guidance or named alternative, but for a unique backup utility the usage context is clear enough to act on.

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