Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

settings

Retrieves KeyCRM account configuration for a chosen section—general, orders, products, leads, currencies, notifications, and more—or returns the full object when no section is set.

Instructions

Account settings (config/settings). section: general, orders, products, leads, currencies, shipment, notifications, companies, suppliers, ai, manufacturing, conversations, tables, order_fields, allowed_fields or empty for the whole object (large).

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

Input Schema

NameRequiredDescriptionDefault
sectionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden and does little: it never states that this is a read-only operation, whether settings can be modified through it, what permissions or auth are needed, or how large 'large' actually is. The only behavioral hint is the parenthetical '(large)' warning about the whole-object response, which is useful but thin for an unannotated tool.

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 dense sentences with no filler; the resource path and the size caveat are front-loaded. The long run-on enumeration of sections is verbosity that is nonetheless functional, since those are the valid values.

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?

For a single-optional-parameter tool with an output schema, the description covers the essential value space, so an agent can call it. It remains incomplete on the fundamentals for an unannotated tool: no statement of read-only semantics, no auth context, and no clarification of how the section values map to the sibling tools of the same names.

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 coverage is 0% and the schema only declares an untyped string with default '', so the description is the sole source of parameter meaning — and it delivers by enumerating the accepted section values (general, orders, products, leads, currencies, shipment, notifications, companies, suppliers, ai, manufacturing, conversations, tables, order_fields, allowed_fields). This meaningfully compensates for the empty schema. It stops short of 5 because case sensitivity, invalid-value behavior, and the empty-string default are not spelled out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (account settings, at config/settings) and enumerates its subsections, so an agent can guess you read config values from here. But no verb is given — it never says 'retrieve' or 'list' — so whether the tool reads, writes, or returns a settings snapshot is inferred rather than stated. The parallels with sibling resource tools like 'orders' and 'products' also leave it unclear whether 'section: orders' returns order settings or an order resource.

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?

There is an implicit usage rule — pass a specific section, or leave it empty for the whole object, which is flagged as '(large)'. That steers agents toward using sections, but there is no explicit when-to-use/when-not-to-use guidance and no mention of how this differs from the many sibling resource tools.

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