Skip to main content
Glama

Banco do Brasil MCP

by io.github.mcp-dir

openfinance_get_account_balance

Read-onlyIdempotent

Returns the latest available balance per account id (GET /accounts/:id/balance). This is the freshest balance the provider can serve, but it is a SNAPSHOT anchored to the connection's last upstream sync: the updateDateTime/updatedAt in each row is that sync instant, NOT a to-the-second live read. If a movement that just happened is not reflected yet, or the balance disagrees with the sum of openfinance_list_transactions, run openfinance_force_sync to pull fresh data and then re-read. Pass account_ids as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR (provider could not fetch it) or BALANCE_CONSENT_ERROR (the institution refused it because the consent lacks the balance permission — reconnecting the bank restores it) — those rows include a structured warning instead of throwing. When the financial institution is temporarily unavailable upstream (5xx) or the connector is not Open Finance, the row DEGRADES to the last-synced balance with realtime: false, updatedAt and a warning instead of an error. Response shape: { results: [...], errors: [{ id, status, message }] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idsYes

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and idempotent, and the description adds substantial context: the balance is a snapshot tied to the last upstream sync, not a live read, and errors can surface as structured warnings instead of thrown exceptions. It even documents specific Pluggy error codes and upstream 5xx degradation behavior.

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 long but every sentence earns its place by covering purpose, freshness semantics, recovery steps, and error behavior. It is front-loaded with the core function and endpoint before diving into caveats.

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?

For a one-parameter read tool with no output schema, the description covers the essential behavioral nuances: staleness, when to force sync, credit-specific errors, warning-vs-throw behavior, and upstream degradation. Agents have enough context to call it correctly and interpret results.

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 input schema only says account_ids is an array of strings, but the description adds the critical array size limit of 1–50 and clarifies they are account IDs. This meaningfully compensates for the 0% schema description coverage, though it stops short of describing each item's expected format or origin.

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 opens with a specific verb and resource: 'Returns the latest available balance per account id' and cites the exact endpoint. This clearly distinguishes it from sibling tools like openfinance_list_transactions and openfinance_force_sync.

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?

The description explicitly tells the agent when to use openfinance_force_sync and re-read if the balance is stale or disagrees with transactions. It also explains how to resolve consent errors by reconnecting the bank, giving clear when-to-use and when-to-do-something-else guidance.

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

All Banco 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

A4/5.0
Disambiguation4/5

Most tools target distinct resources and operations (balance, accounts, loans, investments, connections, provider status), but credit card bill handling is split across three overlapping tools (get_credit_card_bill, list_credit_card_bills, list_transactions), which could cause misselection. The platform-level tools (authenticate, connect, marketplace, etc.) are clearly distinct from the finance tools.

Naming Consistency3/5

The openfinance_* tools mostly follow a verb_noun snake_case pattern (list_accounts, get_account_balance, update_transaction_category), but a few deviate (openfinance_provider_status, openfinance_search_bank_connectors). The non-prefixed platform tools break the pattern entirely with mixed styles: verbs (connect, authenticate), nouns (marketplace), and noun_verb (report_bug, show_version).

Tool Count3/5

At 25 tools, this sits at the high end of reasonable scope. Each Open Finance tool maps to a specific endpoint or workflow, and the platform tools are needed for the MCP meta-layer, but the sheer number makes the set feel heavy and harder to navigate.

Completeness4/5

The Open Finance surface is thorough: connection lifecycle, accounts, balances, transactions, credit card bills, loans, investments, categories, and provider health. Minor gaps exist (e.g., no webhook management, no bulk CSV export), but core workflows are well covered and there are no dead ends.

Resources