Skip to main content
Glama

Nubank MCP

by io.github.mcp-dir

openfinance_list_investments

Read-onlyIdempotent

Returns the investment portfolio for a connection (broker or bank with INVESTMENTS product enabled): FIIs, stocks, ETFs, fixed income (CDB/LCI/LCA/Tesouro), mutual funds, retirement (previdência) and COE. Each row carries balance, amount, amountOriginal, amountProfit, lastMonthRate / annualRate / lastTwelveMonthsRate (when available), dueDate, issuer, ISIN, etc. Returns { total:0, results:[], warning } instead of throwing when INVESTMENTS isn't enabled (403) or other upstream errors. DATA INTEGRITY: when MULTIPLE positions come back as TOTAL_WITHDRAWAL with balance/quantity 0 at once (mass zeroing), the tool cross-checks each position's own transaction history upstream; if the zeroing is contradicted (BUY with no sale/redemption/transfer) the response carries data_integrity_warning and the affected rows are flagged integrity:'suspect_zeroed' — treat those balances as UNAVAILABLE (likely a temporary connector failure publishing zeros), never as real R$0, and do NOT sum them into the portfolio.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNo
pageNo
typeNo
item_idNo
item_idsNo
page_sizeNo

TDQS

A4/5.0
Behavior5/5

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

Annotations already indicate read-only, non-destructive behavior. The description adds critical behavioral details: graceful error handling for disabled INVESTMENTS, data integrity checks (suspect_zeroed flag), and bulk execution via item_ids. No contradictions with annotations.

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 detailed and front-loaded with the core purpose. Each sentence provides value (error handling, data integrity, bulk support). Slightly verbose but appropriate for the complexity.

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 explains the return structure and key fields. It covers error states and data integrity warnings. However, it lacks parameter descriptions, which are part of the tool's context.

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

Parameters1/5

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

The input schema has 6 parameters with 0% description coverage. The description only mentions bulk support via item_ids, leaving page, page_size, type, item, and item_id undocumented. This is a severe gap given low coverage.

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 returns the investment portfolio for a connection, listing specific investment types (FIIs, stocks, ETFs, etc.). It distinguishes from sibling tools like openfinance_list_investment_transactions by focusing on portfolio holdings rather than transactions.

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 that the tool is for retrieving investment portfolios from connections with INVESTMENTS enabled. It covers error handling (returns warning instead of throwing 403) and bulk support. However, it does not explicitly compare against siblings or state when not to use it, though the context is clear.

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