Skip to main content
Glama

Banco do Nordeste do Brasil 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

A3.9/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description discloses cross-checking for mass zeroing, data_integrity_warning, and how to treat suspect rows. It adds value without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose with two paragraphs and detailed data integrity rules. It front-loads the main purpose but could be more concise. Some sentences are long.

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?

Despite no output schema, the description provides rich context: response structure, error handling, data integrity warnings, and bulk support. Lacks parameter documentation, but compensates with overall tool behavior.

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

Parameters2/5

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

With 0% schema description coverage, the description only explains item_ids (bulk support) and indirectly the type parameter by listing types in text. Other parameters (item, page, page_size) are not described, leaving significant ambiguity.

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 it returns the investment portfolio for a connection, listing specific asset types (FIIs, stocks, etc.) and response fields. It distinguishes from sibling tools like openfinance_list_accounts or openfinance_list_investment_transactions by focusing on portfolio holdings.

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 it is for connections with INVESTMENTS product enabled, how errors are handled (returns structure instead of throwing), and provides detailed guidance on handling data integrity warnings. However, it does not explicitly contrast with sibling tools like openfinance_list_investment_transactions.

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

All Banco do Nordeste do Brasil 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
Disambiguation4/5

Most openfinance_* tools target a distinct resource and action, and the descriptions carefully separate overlapping endpoints like openfinance_list_transactions vs openfinance_list_transactions_by_item and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills. The main ambiguity risk is the broad marketplace mega-tool, but its many sub-capabilities are explicitly enumerated.

Naming Consistency4/5

Tool names consistently use snake_case with a strong openfinance_ prefix and verb-led patterns like list_, get_, update_, disconnect_, and force_sync. Minor deviations exist: openfinance_provider_status lacks a verb, openfinance_get_accounts_detail is awkwardly pluralized, and the platform tools (connect, marketplace, authenticate) break from the prefix pattern.

Tool Count3/5

At 25 tools, the server sits at the heavy end of the appropriate range. The Open Finance domain is complex enough to justify most entries, but the inclusion of platform-level tools like marketplace, authenticate, connect, and toolkit_info makes the overall surface feel denser and less focused than a pure banking-data server.

Completeness4/5

The set provides strong coverage of the Open Finance lifecycle: connections, sync/status, accounts, balances, transactions, credit card bills, loans, investments, category management, and provider health. Minor gaps exist, such as no dedicated investment-detail-by-id tool and no way to set custom connection labels, but these are workable and do not create critical dead ends.

Resources