Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

audit

Review recent account changes, inspect modifications to a specific order, lead, task, or manufacturing record, or filter changes by manager.

Instructions

Change history (історія змін, /auditing).

actions: list - recent changes of the whole account (paginated, newest first) by_entity - changes of one object: entity_type (order/lead/task/manufacturing) + entity_id by_manager - changes made by a manager: manager_id Each record has action, model_type, model_ids, initiator and a changes list.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
actionNolist
entity_idNo
manager_idNo
entity_typeNoorder

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior: results are paginated and newest-first, and each record contains action, model_type, model_ids, initiator and a changes list. It says nothing about permission requirements, retention window, or whether history is immutable, which matters for a multi-tenant CRM audit endpoint.

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?

One framing sentence followed by a three-line action table and a one-line record summary. Every line carries information an agent needs, and the action routing is front-loaded before the payload description.

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-value detail is not required, and the description still sketches the record shape. With six optional parameters and no annotations, the main outstanding gap is operational context like auth scope and history depth. For a read-only audit query tool this is otherwise complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the schema contributes only titles and defaults. The description compensates by explaining the action values, the entity_type options (order/lead/task/manufacturing), and the role of entity_id and manager_id relative to each action. Only page/limit are left implicit, and their defaults (1, 20) plus the stated pagination make them self-explanatory.

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?

States a specific resource and verb: change history / audit log, with the endpoint hint (/auditing). The three named actions (list, by_entity, by_manager) make the tool's scope concrete and distinguish it from data-oriented siblings like orders or leads. It stops short of naming a specific sibling to prefer for related reads, but the purpose itself is unambiguous.

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?

The action list functions as mode-selection guidance: pick list for account-wide recent changes, by_entity for one object when you have entity_type + entity_id, by_manager when you have manager_id. This is clear context for choosing within the tool. It does not state when to prefer this tool over alternatives or any exclusions, which keeps it from a 5.

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