Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

crm_status

Checks KeyCRM connectivity and returns the authenticated profile, working channels, token owner, and live counters for orders, clients, products, and users. Use it to start every session.

Instructions

Check KeyCRM connectivity and show account summary.

Returns the authenticated profile, which channels work (internal/official), the API token owner and live counters for orders, pipeline cards, clients, products and users. Start every session with this call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the whole burden: it signals a harmless read via 'Check'/'show' and discloses the shape of the response (profile, channel types, token owner, counters). It does not state what happens on failure, whether the call is rate-limited, or what auth is required to obtain the 'api token owner' detail, and an output schema already exists so listing return contents adds only modest value.

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?

Three short, front-loaded lines: purpose, then return contents, then the call-to-action. Slight redundancy between 'show account summary' and the following 'Returns the authenticated profile...' sentence, but nothing is padded.

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?

A zero-parameter diagnostic with an output schema and no annotations needs little more than what is here: what it checks, what comes back, and when to call it. The only real gap is failure/error behavior for a connectivity check, which is precisely the scenario an agent would most want described.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The text correctly gives no parameter guidance, avoiding noise.

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 two concrete functions: a connectivity check against KeyCRM and an account summary (profile, working channels, token owner, live counters). That is a specific verb+resource pair an agent can act on, though it never explicitly contrasts itself with the similarly scoped siblings crm_capabilities and crm_snapshot.

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?

'Start every session with this call' is an explicit when-to-use instruction and is clearly front-loaded at the end of the description. There are no when-not conditions and no alternative tool is named, so it stops short of full routing guidance.

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