Skip to main content
Glama
ZenMoney MCP Server

ZenMoney MCP Server

by aimuzov

Merchant history

zen_merchant_history

Break down past transactions by merchant ID, payee, or MCC into category usage frequency, totals, and recent examples to resolve ambiguous review rows.

Instructions

Full historical category breakdown for a place (by merchant id, payee text, or mcc): how often each category was used, totals, and recent examples. Use to dig deeper when a review row is ambiguous.

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

Input Schema

NameRequiredDescriptionDefault
toNo
mccNo
fromNo
payeeNo
merchantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavior, and it does disclose the shape of the response (frequencies, totals, recent examples), which signals a read-only analytical lookup. It does not state how 'recent examples' is bounded, whether any key is required, or what happens when several keys are supplied.

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 sentences, front-loaded with the resource and its lookup keys, then the use case. Dense and largely waste-free, though the parenthetical key list sits awkwardly mid-sentence.

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

Completeness3/5

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

All five params are optional, there is no output schema and no annotations, so the description should explain parameter interplay and defaults. It covers output content and intent but leaves date-range filtering and multi-key precedence unspecified.

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 description coverage is 0% across 5 params, and the description only accounts for three of them (merchant, payee, mcc). The from/to date-range parameters — potentially the key scoping inputs for a 'historical' tool — are never mentioned, leaving a real gap the schema does not fill.

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 resource and scope: historical category breakdown per merchant, with the three lookup keys (merchant id, payee text, mcc) and the returned content (usage frequency, totals, recent examples). It implicitly distinguishes itself from zen_review_expenses via 'when a review row is ambiguous,' though no sibling is named outright.

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?

'Use to dig deeper when a review row is ambiguous' gives a concrete triggering condition that routes the agent away from the review tool. No when-not guidance or explicit named alternative (e.g. zen_find_transactions vs this) is offered.

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