Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

crm_endpoints

Search 572 internal KeyCRM API routes by query or group to find exact paths and methods before calling crm_api.

Instructions

Search the reverse-engineered endpoint catalog (572 internal API routes).

Use it to find the exact path+method before calling crm_api, e.g. query="tags", group="finance", query="export".

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

Input Schema

NameRequiredDescriptionDefault
groupNo
limitNo
queryNo

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 full burden; it does disclose that the catalog is reverse-engineered (implying non-authoritative, possibly stale data) and that it contains 572 routes. It does not state paging behavior or what happens when nothing matches, though the output schema covers return shape.

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?

Two short lines, front-loaded with the core purpose and followed by the workflow instruction. The example string is slightly malformed (it lists `query` twice and concatenates two examples), which adds minor noise.

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

Completeness3/5

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

The presence of an output schema removes the need to describe returns, and the workflow context is solid. However, with zero schema descriptions across three parameters, the description should have explained what `group` and `limit` actually do; that gap keeps it at adequate rather than complete.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate: it does so partially by naming `query` and `group` and giving sample values ('tags', 'finance', 'export'). The `limit` parameter is never mentioned, and the meaning of `group` (endpoint grouping/tagging) is left implicit.

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?

"Search the reverse-engineered endpoint catalog (572 internal API routes)" gives a specific verb and resource with explicit scope and provenance. It also implicitly distinguishes itself from crm_api by positioning the catalog lookup as the precursor to that call.

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?

"Use it to find the exact path+method before calling crm_api" states a clear use condition and names the downstream alternative. It stops short of saying when this tool is unnecessary (e.g. if the route is already known or is a common CRUD path).

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