Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

finance

Read bills, payments, currency rates, fiscal receipts, bank transactions, and billing details from KeyCRM without changing monetary records.

Instructions

Finance (фінанси): bills, payments, dictionaries, currency, billing.

Read only on purpose: creating or moving money objects is risky, so the tool never writes. Actions: bills / accounts - list finance bills (рахунки), filters passed as-is payments - list payments (answers 500 on this tenant, server side) payment_config - payment form config: min/max amounts, methods, managers expense_types - expense type dictionary payment_methods - payment method dictionary payment_gateways - connected payment gateways currency_rates - account currency rate table rates_common - common currency rates; currency="USD,UAH" narrows it fiscals - fiscal receipts / registers transactions - bank transactions (answers 500 on this tenant) transactions_config / transactions_unlinked - bank import config / unlinked rows billing - account balance, tariff and usage counters billing_invoices / billing_payments - subscription invoices and charges Example filters: {"filter[status]": "new"}; keys are sent as-is.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
actionNobills
filtersNo
currencyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it declares a deliberate read-only contract ('never writes' because money mutation is risky), warns that 'payments' and 'transactions' return 500 on this tenant, and notes filters/keys are passed through as-is. It does not describe pagination behavior or how filters interact per action, which keeps it below 5.

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 read-only rationale is front-loaded, followed by a scannable action list where each line earns its place. The per-action enumeration is long but functional; the only redundancy is restating 'payment form config' style glosses that could be tighter.

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?

For a multi-action dispatcher with an output schema already covering return values, the definition gives enough to call it correctly: the action vocabulary, filter passthrough semantics, a currency narrowing rule, and known server-side failures. Pagination defaults and per-action filter constraints are the remaining gaps.

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 does for the two parameters that carry real semantic load: 'action' is enumerated with about fourteen named values, and 'filters' is illustrated with a concrete example plus the 'keys sent as-is' rule, with 'currency' scoped explicitly to rates_common. Only 'page' and 'limit' are left unexplained, which is a minor gap for otherwise self-evident parameters.

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 specific resource domain (finance: bills, payments, dictionaries, currency, billing) and enumerates the actions it exposes, so an agent knows exactly what the tool reaches. It does not explicitly contrast itself with siblings like 'orders' or 'clients', but the finance scoping 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?

Each action is listed with the resource it returns (bills/accounts, payments, payment_config, expense_types, currency_rates, fiscals, transactions, billing, etc.), which is effectively an action-selection guide. What's missing is an explicit statement of when this tool is preferable to a sibling tool for overlapping data.

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