Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

custom_fields

List custom field definitions, fetch one definition by ID, or retrieve values for a specific lead, order, or client.

Instructions

Custom fields (кастомні поля): definitions and values.

Actions: list - all custom fields; model filters them (lead / order / client) values - entity_id + model required; values of that object field - field_id required; one definition from the list Note the values path order: /config/custom-fields/{entity_id}/{model}/values.

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

Input Schema

NameRequiredDescriptionDefault
modelNo
actionNolist
field_idNo
entity_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden; all three actions read as retrieval operations, but read-only status, permissions, and pagination/empty-result behavior are never stated. It does add one non-obvious implementation detail about the values path ordering, which is genuine context beyond structured fields.

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 action list is front-loaded and each line earns its place by pairing an action with its required inputs. The trailing note on URL path order is marginal value and slightly distracts from the actionable content, but it is brief.

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 return values need not be spelled out, and the description covers the action selection and per-action parameter requirements. Remaining gaps are modest: the default action, whether 'model' is optional for list, and failure behavior for an unknown action.

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 description coverage is 0%, so the description must compensate, and it largely does: it explains that 'model' filters list results (lead/order/client) and is required for the values action, that field_id identifies a single definition, and that entity_id targets a specific object. The action enum values themselves are only documented in prose, which the description supplies.

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 resource (custom field definitions and their values) and enumerates three distinct actions with what each returns, so an agent knows exactly what capability this exposes. It does not, however, differentiate itself from plausible siblings such as settings or leads/orders, so the boundary is left implicit.

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?

Useful per-action prerequisites are given (entity_id + model for 'values', field_id for 'field'), which effectively tells the agent how to select the right action. There is no guidance on when this tool should be preferred over sibling tools, and the default action ('list') is only visible in the schema, not called out.

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