Skip to main content
Glama
Iyongbudiarso

moneylover-mcp

by Iyongbudiarso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

summarize_spending

Read-only

Calculate total income or expenses by category and currency over a date range, answering 'how much did I spend on X' or 'what did I earn this month'.

Instructions

Total income or expenses per category over a date range, grouped by currency: the answer to 'how much did I spend on X' or 'what did I earn this month'. Use it for every total or comparison; use list_transactions for individual entries and list_categories to see which categories exist. Behavior: currencies are never added together, so the response has one entry per currency with its own total and category breakdown, largest first. Without a wallet, every wallet is totalled, also archived ones and those excluded from Money Lover's total; pass wallet to narrow it. Transactions flagged 'exclude from report' are left out (list_transactions still shows them). With no activity in the range the currency list is empty, not zero-filled. The range is inclusive and limited to 366 days per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoWhich side to total: "expense" (spending) or "income" (earnings). Defaults to "expense".
walletNoWallet name, exactly as returned by list_wallets. Omit to total across all wallets, including archived ones and those excluded from Money Lover's total.
end_dateYesLast day of the range, inclusive, as YYYY-MM-DD. Must not be before start_date; the whole range may span at most 366 days.
start_dateYesFirst day of the range, inclusive, as YYYY-MM-DD in the user's timezone, e.g. "2026-04-01".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesReminder that transactions flagged "exclude from report" are not counted.
typeYes
end_dateYesLast day of the range, inclusive.
currenciesYesOne entry per currency; amounts in different currencies are never added together.
start_dateYesFirst day of the range, inclusive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • changedInput schema / properties / end_date / description
      Previous value: -"Last day, inclusive, as YYYY-MM-DD."New value: +"Last day of the range, inclusive, as YYYY-MM-DD. Must not be before start_date; the whole\nrange may span at most 366 days."
    • changedInput schema / properties / start_date / description
      Previous value: -"First day, inclusive, as YYYY-MM-DD."New value: +"First day of the range, inclusive, as YYYY-MM-DD in the user's timezone, e.g. \"2026-04-01\"."
    • changedInput schema / properties / type / description
      Previous value: -"Which side to total. Defaults to expense."New value: +"Which side to total: \"expense\" (spending) or \"income\" (earnings). Defaults to \"expense\"."
    • changedInput schema / properties / wallet / description
      Previous value: -"Wallet name. Omit for all wallets."New value: +"Wallet name, exactly as returned by list_wallets. Omit to total across all wallets, including\narchived ones and those excluded from Money Lover's total."
  2. Changed9 schema fields changedv0.3.2
    • addedOutput schema / $defs / CategoryTotal / properties / category / description
      Added value: +"Category name; sub-categories are reported under their own name."
    • addedOutput schema / $defs / CategoryTotal / properties / count / description
      Added value: +"Transactions counted in this category."
    • addedOutput schema / $defs / CategoryTotal / properties / total / description
      Added value: +"Decimal string summed in this currency only."
    • addedOutput schema / $defs / CurrencySummary / properties / count / description
      Added value: +"Transactions counted in this currency."
    • addedOutput schema / $defs / CurrencySummary / properties / currency / description
      Added value: +"ISO currency code, or UNKNOWN when the wallet's currency could not be read."
    • addedOutput schema / $defs / CurrencySummary / properties / total / description
      Added value: +"Decimal string: the sum of every category below."
    • addedOutput schema / properties / end_date / description
      Added value: +"Last day of the range, inclusive."
    • addedOutput schema / properties / note / description
      Added value: +"Reminder that transactions flagged \"exclude from report\" are not counted."
    • addedOutput schema / properties / start_date / description
      Added value: +"First day of the range, inclusive."
  3. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, and the description fills in substantial non-obvious behavior: currencies are never summed together, one entry per currency sorted largest first, empty result rather than zero-filled when there is no activity, and report-excluded transactions are dropped here but still visible in list_transactions. The inclusive 366-day range cap is also disclosed.

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?

Front-loads the core purpose and routing guidance, then groups remaining details under an explicit 'Behavior:' marker. It is dense and longer than most definitions, but nearly every clause carries non-obvious semantics rather than restating the name or schema.

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

Completeness5/5

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

For a grouped-aggregate read tool with an output schema (so return values need not be explained) and full schema coverage, the description is complete: it covers routing, currency grouping, ordering, empty-result behavior, exclusion rules, and the date-range constraint.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds parameter-relevant behavior not present in the schema: transactions flagged 'exclude from report' are omitted, and the wallet-omitted case totals archived and Money Lover-excluded wallets. The archived-wallet nuance partially repeats the schema text, but the exclusion semantics are genuinely additive.

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 ('Total income or expenses per category over a date range, grouped by currency') and frames the exact question it answers. It explicitly distinguishes itself from list_transactions (individual entries) and list_categories (which categories exist), so an agent can route without opening sibling schemas.

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?

Explicit when-to-use ('Use it for every total or comparison') and names the alternatives with their selecting conditions ('list_transactions for individual entries and list_categories to see which categories exist'). It also gives the conditional guidance for the wallet parameter (omit to total all, pass to narrow).

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

Deploy Server

Other Tools