Skip to main content
Glama
ZenMoney MCP Server

ZenMoney MCP Server

by aimuzov

Review expenses

zen_review_expenses

Audit expenses in a date range to find uncategorized or mis-categorized transactions, each with ranked category candidates inferred from your history at the same place, ready for your review.

Instructions

Audit expenses in a date range: returns those that are uncategorized or likely mis-categorized, each with the current category and ranked candidate categories (with confidence) inferred from history at the same place. YOU decide the final category from this evidence, then propose changes via zen_apply_categories. Run zen_sync first if the cache may be stale.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "zen_review_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd date, inclusive (YYYY-MM-DD)
fromYesStart date, inclusive (YYYY-MM-DD)
limitNo
accountNoLimit to one account id
includeOkNoAlso include expenses that look fine (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return contents (current category, ranked candidates with confidence, inferred from history at the same place) and implicitly establishes that this tool is read-only — decisions and writes happen elsewhere. It is silent on ordering, truncation at the 300 limit, and any cost/latency of the history inference.

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?

Three sentences, front-loaded with purpose, then output semantics, then the required next step. No filler and no repetition of schema fields.

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?

No output schema exists, and the description compensates by describing the returned shape and its meaning in enough detail to act on. The remaining gap is behavioral detail around limit/truncation and result ordering for a 5-parameter tool.

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

Parameters3/5

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

Schema coverage is 80%, so the baseline is 3; from/to are documented in the schema. The description only implicitly touches includeOk by framing the default as uncategorized/mis-categorized items, and says nothing about how limit or account interact with the audit output.

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?

States a specific verb and resource ('Audit expenses in a date range') and immediately defines the result set: uncategorized or likely mis-categorized items. This distinguishes it cleanly from siblings like zen_find_transactions (search) and zen_merchant_history (lookup history at one merchant).

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

Usage Guidelines5/5

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

Explicitly routes the agent: it decides the final category itself and then proposes changes via zen_apply_categories, and should run zen_sync first if the cache may be stale. Both the next step and the prerequisite are named, so the workflow is unambiguous.

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