Zen Money MCP

suggest_transactions

Get Zen Money suggestions for multiple transactions in one batch request, helping categorize or complete several financial operations at once.

Instructions

Получить подсказки Дзен-мани сразу для нескольких операций через пакетный /v8/suggest/.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transactions": "<transactions>"
    },
    "name": "suggest_transactions"
  }
}

Input Schema

Name	Required	Description	Default
`transactions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only states that this uses the batch /v8/suggest/ endpoint and returns suggestions; it does not disclose permissions, limits, side effects, response shape, or failure behavior.

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?

A single, front-loaded sentence that directly states the tool's purpose and endpoint with no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch tool accepting an array of up to 100 nested transaction objects, with no annotations, no output schema, and 0% schema description coverage, the description is too sparse. It lacks input field guidance, output expectations, and batch constraints beyond the endpoint name.

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

Parameters2/5

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

Schema description coverage is 0%, and the nested transaction fields (date, payee, amount, comment) are undocumented. The description only conveys that multiple operations are accepted, without adding meaning beyond the array structure already in the schema.

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

Purpose5/5

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

The description states a specific verb and resource: get Zenmoney suggestions for several operations at once via the batch endpoint. It explicitly distinguishes itself from the singular sibling suggest_transaction by emphasizing batch/multiple operations.

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?

The phrase 'сразу для нескольких операций' implies when to use this batch tool rather than the singular suggest_transaction, but it does not explicitly state when to prefer one over the other or any prerequisites.

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