Zen Money MCP

list_accounts

Retrieve accounts, currencies, and balances from Zen Money, with an option to include archived accounts, to review personal financial status.

Instructions

Показать счета, валюты и балансы.

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

Input Schema

Name	Required	Description	Default
`includeArchived`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. "Показать" implies a read operation, but the description does not confirm read-only behavior, explain the effect of the includeArchived parameter, describe permissions, or clarify the returned structure beyond mentioning accounts, currencies, and balances.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no filler and is front-loaded. However, it is too terse to convey the necessary details about filtering and output for a list tool.

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 simple list tool with one optional boolean parameter and no annotations or output schema, the description should at least explain default filtering and what the returned fields represent. It mentions accounts, currencies, and balances but leaves the includeArchived behavior and read-only nature unstated.

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

Parameters1/5

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

The schema has 0% description coverage and one optional parameter, includeArchived. The description does not mention this parameter or explain how it changes the result, so it fails to compensate for the schema 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?

The description states a specific verb and resource ("Показать счета" – show accounts) and adds that currencies and balances are included, making the tool's output scope clear. It does not explicitly distinguish itself from related tools such as get_zenmoney_entities, but the account-listing purpose is evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus siblings like get_zenmoney_entities, create_account, update_account, or archive_account. It also does not say whether archived accounts are included or excluded by default.

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