Skip to main content
Glama

Nubank MCP

by io.github.mcp-dir

openfinance_list_transactions_by_item

Read-onlyIdempotent

Consolidated cash-flow analysis for a whole bank CONNECTION over a period, in ONE call. Resolves the connection's accounts internally and fans out their transactions, so you do NOT need to call openfinance_list_accounts first nor carry account_id uuids between calls. Pass item (connector_id, connector_name or item_id) to target one bank, or OMIT it to analyze ALL linked banks at once. from/to are ISO dates (YYYY-MM-DD). Default granularity:'monthly' returns a COMPACT summary (no raw rows): total entradas, saídas, saldo_liquido, monthly evolution (por_mes), and top_despesas/top_recebimentos (largest N each), plus a per-account breakdown (by_account). Use this for 'análise anual/mensal', 'fluxo de caixa', 'entradas e saídas', 'maiores gastos/recebimentos'. Set granularity:'raw' to ALSO get every consolidated transaction (heavier — only when itemized rows are needed); combine with detail:'rich' to enrich those rows with merchantInfo (cnpj/cnae/businessName/category) + extra creditCardMetadata (billId, purchaseDate, fees), or detail:'raw' for the full untouched Pluggy object per row, when the connector provides them. type filters BANK or CREDIT accounts. On a connection with many transactions the scan caps at 5000/account and flags truncated:true. May include a provider_incident block when the Open Finance provider has an OPEN incident affecting a connected bank: the totals/rows may be incomplete or wrong until the provider recovers, and reconnecting does not fix it.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
fromNo
itemNo
typeNo
top_nNo
detailNo
item_idNo
item_idsNo
granularityNo

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds critical behaviors: a cap of 5000 transactions per account with a 'truncated:true' flag, and a 'provider_incident' block indicating possible incomplete results due to provider issues. These are valuable for safe invocation.

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?

The description is comprehensive and well-organized, starting with purpose and then systematically covering parameters and behaviors. While it is lengthy, every sentence provides essential information, and the front-loaded purpose helps agents quickly grasp the tool's role.

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?

Given no output schema, the description adequately outlines the return format (compact summary with totals, monthly evolution, top items, per-account breakdown; raw rows with optional enrichment). It also covers limitations (truncation, provider incidents) and bulk support. Minor ambiguity remains about the interaction between 'granularity' and 'detail'.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by detailing all parameters: item (connector_id/connector_name/item_id), from/to (ISO dates), granularity (monthly vs raw), detail (compact/rich/raw), type (BANK/CREDIT), top_n (implied for top expenses), and bulk item_ids. It adds meaning beyond the schema's bare structure.

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 clearly states the tool performs consolidated cash-flow analysis for a whole bank connection in one call, avoiding the need for separate account listing. It distinguishes itself from sibling tools like openfinance_list_transactions by resolving accounts internally. The verb 'list_transactions_by_item' is accurately reflected.

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?

The description explains when to use this tool (for consolidated analysis) and when to use alternative granularities ('raw' only when itemized rows needed). It also mentions bulk support via item_ids. However, it does not explicitly exclude scenarios where other tools like openfinance_list_accounts might be better, but the context is clear enough.

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

All Nubank MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Most openfinance_* tools target distinct resource/action pairs, but there is real overlap among list_accounts, get_accounts_detail, and get_account_balance, as well as between list_transactions and list_transactions_by_item, and between get_credit_card_bill and list_credit_card_bills. The descriptions are detailed enough to usually resolve ambiguity, but the number of near-overlapping read/status tools makes mis-selection plausible.

Naming Consistency4/5

The 21 openfinance_* tools follow a clear openfinance_<verb>_<noun> convention with predictable verbs like list, get, update, force, disconnect, and search. The non-prefixed platform tools (authenticate, connect, marketlace, report_bug, show_version, toolkit_info) break the pattern but are few enough to keep the naming mostly coherent.

Tool Count3/5

25 tools is at the heavy end for the stated banking domain, and several could reasonably be merged: get_account_balance/get_accounts_detail/list_accounts and list_transactions/list_transactions_by_item overlap in purpose. The breadth of resources covered accounts, cards, loans, investments, connections, and provider health helps justify the count, but it still feels slightly bloated.

Completeness5/5

The Open Finance workflow is thoroughly covered: connect discover, force sync, status checks, accounts, balances, transactions, credit-card bills, loans, investments, category correction, disconnection, and provider health. Edge cases like stale data, consent errors, provider incidents, and cross-connector asymmetries are explicitly handled, leaving no obvious dead ends for an agent.

Resources