Skip to main content
Glama
Zen Money MCP

Zen Money MCP

by bulava92

get_zenmoney_entities

Retrieves complete raw ZenMoney API records for any entity, including reminderMarker, so you can access all fields and filters missing from summary tools.

Instructions

Получить полные исходные записи любой сущности ZenMoney API, включая reminderMarker. Используй для доступа ко всем полям и фильтров, которых нет в кратких инструментах.

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": {
      "entity": "<entity>"
    },
    "name": "get_zenmoney_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
entityYes
offsetNo
searchNo
toDateNo
fromDateNo
includeDeletedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 burden. It hints that records are 'полные исходные записи' (full raw records), but says nothing about pagination via limit/offset, what includeDeleted actually does, date-range semantics, or permissions/return shape. For a 7-parameter read tool with zero annotation coverage this is a significant gap.

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?

Two front-loaded sentences with no filler; the scope is stated first and the usage cue second. Appropriately sized for the tool, though the brevity comes at the cost of the missing detail noted elsewhere.

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?

With 7 parameters at 0% schema coverage, no annotations, and no output schema, the description should explain filtering and pagination but does not. An agent cannot tell from the text how limit/offset/date filters interact or what deleted-record inclusion means, leaving it under-specified for a general-purpose entity fetcher.

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 there are 7 parameters, yet the description explains none of them. It mentions reminderMarker as one entity value, but limit, offset, search, fromDate/toDate, and includeDeleted are all left undocumented in both schema and description. Marginal value over the structured fields.

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 (get) and resource (full raw records of any ZenMoney entity), and calls out reminderMarker specifically. It implicitly distinguishes itself from the many list_* siblings by framing them as 'краткие инструменты' (brief tools), though it does not name them. Clear enough that an agent knows this is the full-fidelity fetcher.

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?

'Используй для доступа ко всем полям и фильтров, которых нет в кратких инструментах' gives an explicit when-to-use and points at the alternative category (the brief list_* tools). It stops short of naming specific siblings or stating when-not to use it, so it is not a full 5.

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