Skip to main content
Glama
Sign In

BankBridge

by money.bankbridge
OverviewDiscussionsAdmin

List Transactions

list_transactions
Read-onlyIdempotent

List transactions across connected accounts, newest first, with optional filters for date range, account, category, amount, and pending status. Positive amounts are money spent; negative amounts are money received. Default window is the last 30 days; banks provide up to 24 months. Paginated with limit/offset (default 50, max 100); the response includes total_count and has_more. Each call reads the bank live and banks allow about 30 reads a minute, so totals by category, merchant or month come from get_spending_summary or get_monthly_cashflow in one call rather than from paging through every transaction; when paging is needed, limit=100 keeps the number of calls down. The response includes a warnings array of notices about banks that could not contribute (for example, a bank that needs reconnecting), each with a message and, when relevant, a reconnect_url.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1 to 100). Defaults to 50.
offsetNoNumber of results to skip, for paging. Defaults to 0. Use with has_more.
pendingNoSet to false to leave out pending (not yet posted) transactions.
categoryNoSpending category, case-insensitive. One of: INCOME, TRANSFER_IN, TRANSFER_OUT, LOAN_PAYMENTS, LOAN_DISBURSEMENTS, BANK_FEES, ENTERTAINMENT, FOOD_AND_DRINK, GENERAL_MERCHANDISE, HOME_IMPROVEMENT, MEDICAL, PERSONAL_CARE, GENERAL_SERVICES, GOVERNMENT_AND_NON_PROFIT, TRANSPORTATION, TRAVEL, RENT_AND_UTILITIES, OTHER.
end_dateNoDate in YYYY-MM-DD format. Defaults to today.
account_idNoLimit results to a specific account. Use an account id returned by list_accounts.
max_amountNoOnly transactions whose absolute amount is at most this many dollars.
min_amountNoOnly transactions whose absolute amount is at least this many dollars.
start_dateNoDate in YYYY-MM-DD format. Defaults to 30 days ago.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only and open-world annotations, the description discloses live bank reads, an approximate rate limit of 30 reads per minute, default and maximum date windows, pagination behavior, and a warnings array with reconnect URLs for unavailable banks.

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?

The description is dense but front-loaded, opening with the core purpose and then layering only operationally useful details: amount sign, defaults, pagination, rate limits, aggregation alternatives, and warnings. Every sentence contributes information an agent needs to call the tool correctly.

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?

With nine optional parameters, live external bank data, and no output schema, the description provides the missing operational context: response pagination fields, warning behavior, rate limits, defaults, and when to prefer sibling aggregate tools.

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?

The schema already covers all parameters at 100%, so the baseline is 3, but the description adds the important sign convention that positive amounts are spending and negative amounts are income. It also clarifies the default date window and practical limit choice even though some of those details overlap the schema.

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?

The description states a specific verb and resource: list transactions across connected accounts. It adds scope details such as newest-first ordering and optional filters, which let an agent distinguish it from the summary-oriented siblings it names.

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?

It explicitly redirects aggregate needs to get_spending_summary and get_monthly_cashflow, explaining that paging through transactions is the wrong approach for totals. It also gives paging guidance to use limit=100 when paging is unavoidable.

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

All BankBridge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources