Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

products

Manage a KeyCRM catalog: list stock levels, retrieve, create, update, delete items, browse categories and warehouses, and search records.

Instructions

Catalog products (товари).

actions: list (with stock quantity), get, create (name required), update, delete, categories (tree), warehouses, search.

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

Input Schema

NameRequiredDescriptionDefault
dataNo
pageNo
limitNo
actionNolist
searchNo
product_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 and only partially discharges it by noting that create requires a name, list includes stock quantity, and categories returns a tree. It does not disclose delete destructiveness, permission requirements, reversibility, side effects, rate limits, or consequences of update operations.

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 short, front-loaded with the resource name, and organized as a compact action list with minimal wasted wording. The compressed format is appropriate, though the parenthetical translation and terse action enumeration leave important details implicit.

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?

An output schema exists, so return-value explanation is less necessary, but this is a complex multi-action tool with mutations, six parameters at 0% schema coverage, and no annotations. The description lists actions but omits most parameter semantics, safety context for delete, and operational details needed for correct invocation.

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 description coverage is 0% across six parameters, so the description must compensate. It documents action values and the create name requirement, but leaves data, page, limit, search, and product_id unexplained, and it does not clarify how product_id maps to get, update, or delete.

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 states a specific resource, 'Catalog products', and enumerates its multi-action scope including list, get, create, update, delete, categories, warehouses, and search. It is clear what the tool does overall, though it does not explicitly distinguish itself from sibling tools such as stocks or orders.

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

Usage Guidelines3/5

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

The action list implies which operation to invoke for common intents, such as using 'get' for retrieval or 'create' with a required name for creation. However, it gives no explicit when-to-use versus sibling-tool guidance, no prerequisites, and no exclusions for actions like delete or categories.

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