Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

automations

List and inspect read-only KeyCRM automation triggers, filtering by event, group, or active status to understand live CRM behavior without creating or editing them.

Instructions

Automation triggers (автоматизації), read only.

Actions: list - all triggers, compact; event / group / is_active filter locally get - trigger_id required; one trigger from the list Creation, editing and toggling are not exposed: a trigger changes live CRM behaviour.

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

Input Schema

NameRequiredDescriptionDefault
eventNo
groupNo
actionNolist
is_activeNo
trigger_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only scope, notes that event/group/is_active are applied client-side ("filter locally") rather than server-side, and marks list output as "compact." It does not mention pagination, result limits, or auth requirements, which keeps it short of a 5.

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?

Front-loaded scope statement followed by a scannable action list and a single justification sentence. Nothing is redundant and the constraint is stated before the mechanics.

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 described, and the description covers the action space, prerequisite for get, and the reason no mutations exist. The notion of "compact" list output and how local filtering interacts with result size are the only unresolved details.

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 covers all five parameters semantically: action via the Actions list, event/group/is_active as filters, trigger_id as required for get. It adds no value-format detail (allowed event strings, group identifiers), which is the remaining gap.

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 verb+resource ("Automation triggers ... read only") and enumerates the two actions. It is instantly clear what domain the tool covers, though it never contrasts itself with any sibling tool, so the agent must infer it is the only automation surface from names alone.

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?

Explicitly distinguishes list vs get ("trigger_id required") and rules out write operations, explaining why: "a trigger changes live CRM behaviour." That is strong when-to-use guidance with an exclusion, but it names no alternative tool for creating/editing automations, so the agent is left to search elsewhere unaided.

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