Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

crm_capabilities

Discover the active modules, plan flags, API request limits, and known broken endpoints of the connected CRM account so agents can plan calls and avoid dead routes.

Instructions

What this CRM account can do right now.

Returns active modules (orders, leads, conversations, ...), plan-level flags, the API request limit and the list of known broken or quirky endpoints, so the model does not waste calls on dead routes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses what the response covers (modules, plan flags, request limit, broken routes), but never says whether the call is read-only, whether it requires authentication or elevated plan access, or whether results are cached/stale – all material for a capability probe.

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

Conciseness5/5

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

Three compact lines: purpose first, then payload, then the reason it matters. No filler, no restatement of the name, and the rationale is folded into the return-value sentence rather than padding.

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 the description only needs to frame the payload, which it does at a useful summary level. The main residual gap is the absence of any environment/permission caveat for a tool whose whole value is telling the agent what is available.

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 there is no parameter meaning to convey and the baseline for an empty schema applies. Nothing in the description conflicts with the empty input 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 states a concrete discovery purpose ('What this CRM account can do right now') and enumerates the payload: active modules, plan-level flags, API request limit, known broken endpoints. It does not distinguish itself from plausible siblings like crm_status or crm_endpoints, so the boundary must be inferred.

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?

Usage is only implied via the rationale 'so the model does not waste calls on dead routes' – an agent can infer it should be consulted before hitting other CRM routes. There is no explicit 'call this first', no stated exclusions, and no named alternative for status or endpoint listing.

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