Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

files

List, upload, download, validate, detach, or delete KeyCRM order attachments and files, including base64 uploads up to 250 MB per order.

Instructions

Files and attachments (файли) of orders.

actions: list_order - attachments of an order (GET /orders/{id}, field attachments) validate - size limit check before upload: order_id + path attach_order - upload a file to an order: order_id + path (local file) or content_base64, optional filename/mime; multipart, single chunk, limit 250 MB per order download - save a file by file_id into keycrm-mcp/exports/, returns local path, size and content type detach - remove attachment from its entity (attachment_id) delete_file - delete file itself (file_id), cascades attachments

Note: deleting an order does NOT delete its files, remove orphans with delete_file explicitly.

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

Input Schema

NameRequiredDescriptionDefault
mimeNo
pathNo
actionNolist_order
file_idNo
filenameNo
order_idNo
attachment_idNo
content_base64No

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 250 MB per-order limit, single-chunk multipart upload, that download writes to a local exports path and returns path/size/content type, and that delete_file cascades to attachments. It omits permission/auth requirements and irreversibility warnings for the delete actions, which is the remaining gap.

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 with a one-line purpose followed by a scannable action list, each entry earning its place with the endpoint or constraint. Slightly dense but no filler sentences; the final note is short and adds real value.

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

Completeness5/5

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

For a six-action multiplexed tool with an output schema already covering return shapes, the description supplies action routing, key parameters, size limits, storage location, and cascade behavior. Nothing essential to calling it correctly is missing.

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% across 8 parameters, so the description must compensate, and it largely does by binding parameters to actions: order_id + path for validate, order_id + path or content_base64 with optional filename/mime for attach_order, file_id for download/delete_file, attachment_id for detach. Types, defaults, and the fact that no parameter is strictly required are left to 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?

The description names the resource ('files and attachments of orders') and then enumerates six concrete actions with the verb and target of each (list_order, validate, attach_order, download, detach, delete_file). An agent can tell detach from delete_file purely from this text. It does not differentiate itself from siblings like documents or orders, which keeps it short of a 5.

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?

Usage context is embedded per action: validate is 'size limit check before upload', download saves into a specific exports directory, detach removes the link while delete_file removes the file itself. The closing note explains the orphan-file scenario that motivates calling delete_file. No explicit statement about when to prefer this tool over a sibling, but the intra-tool routing is unambiguous.

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