Skip to main content
Glama

Summarize transactions

wave_summarize_transactions
Read-onlyIdempotent

Totals matching transactions by category, month, vendor, customer, or account to answer spending and income questions without paging individual records.

Instructions

Totals over every matching transaction, grouped by category, month, vendor, customer or bank/card account: how much was spent on Marketing this year, spend per month, top vendors. Pages through Wave itself and returns only the totals, so use it instead of paging wave_list_transactions to add things up. Same filters as wave_list_transactions. Sums line amounts (which include sales tax): money-out lines (debits) are withdrawals, money-in lines (credits) are deposits; journal entries count by the same debit/credit rule. With categoryIds, only the lines in those categories count, so split transactions are not double counted. Uses Wave's web-app API (unofficial), which needs a web session: if it is missing or expired, the user runs node /app/bin/wave-mcp.js login in a terminal on 1c94a9392181.

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

Input Schema

NameRequiredDescriptionDefault
searchNoText in the transaction description or a line description (case-insensitive)
sourceNoWhere it came from: MANUAL = statement upload; PLAID/YODLEE/CASHEDGE = bank connection; GENERIC_EXTERNAL_API = API (wave_create_transaction); RECEIPT/RECEIPT_CAPTURE = receipts. Entries typed into Wave have no source
endDateNoLatest transaction date (inclusive)
groupByNoaccount = the bank/card account; none = totals onlycategory
accountIdNoBank or card account (wave_list_accounts): transactions paid from or into it. An income/expense category given here is treated as categoryIds
maxGroupsNoLargest groups to return; the rest are added up in otherGroups
startDateNoEarliest transaction date (inclusive)
businessIdNoBusiness ID; defaults to the one wave_get_context reports
categoryIdsNoCategory accounts (income/expense, wave_list_accounts with search): transactions with a line in any of them
uncategorizedOnlyNoOnly transactions still in Uncategorized Income/Expense

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that the tool pages through Wave internally and returns only totals, that sums are over line amounts including sales tax, that debits are withdrawals and credits are deposits, that journal entries follow the same rule, and that categoryIds filters at the line level so split transactions are not double counted. It also surfaces the non-obvious auth dependency (unofficial web-app API, expired session requires a terminal login command), which the annotations do not cover.

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 capability and grouping options, then layers on accounting semantics and the auth caveat; nearly every sentence carries information. A few sentences are dense run-ons, and the hostname in the login instruction is environment-specific noise, but nothing is filler.

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?

For a 10-parameter aggregation tool with no output schema, it covers the aggregation semantics, filter behavior, and auth prerequisite thoroughly. The remaining gap is the shape of the response itself (group keys, the totals field, and the otherGroups overflow) which is only implied by the maxGroups schema description rather than stated in the description.

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 is 3, but the description adds genuine meaning the schema does not: categoryIds restricts which lines count within a transaction, which changes the meaning of the totals rather than just filtering rows. It also frames the parameter set as equivalent to wave_list_transactions, helping the agent reason about the filter combination.

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 ('Totals over every matching transaction') and enumerates the grouping dimensions (category, month, vendor, customer, bank/card account) with concrete example questions. It explicitly distinguishes itself from wave_list_transactions, so an agent can route between the two without opening a schema.

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?

Gives an explicit when-to-use rule: 'use it instead of paging wave_list_transactions to add things up,' and states the filters are the same as that sibling, which tells the agent it can reuse the same query shape. The one exclusion an agent could get wrong (manual paging to sum) is called out directly.

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