Skip to main content
Glama

Banco do Brasil MCP

by io.github.mcp-dir

openfinance_search_bank_connectors

Read-onlyIdempotent

Searches the available bank connectors by name (pass keywords[], e.g. ['nubank','btg']) and returns, per match: the connector id, whether it's Open Finance or API (access), PF/PJ (audience), the user's already-linked connections (and accounts when include_accounts=true), and a ready connect_url with the bank pre-selected. Some non-Open-Finance credential connectors carry a caveat warning that they don't auto-update (needs periodic manual reconnection) — surface it so the user can prefer the institution's Open Finance connector for automation. Honors the user's plan (a PF plan hides PJ banks; a PJ plan covers BOTH — PF and PJ banks connect and count under the same plan). Call this BEFORE connecting to hand the user a one-click link to the right bank. keywords[] is REQUIRED — without it returns a hint (never dumps the whole catalog).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNo
include_accountsNo

TDQS

A4.6/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it discloses caveats for non-Open-Finance connectors, plan-based filtering (PF vs PJ), and the behavior when no keywords are provided. This fully informs the agent of the tool's behavior.

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 well-structured and front-loaded with the main action. Every sentence adds value, though it is slightly verbose. It could be tightened without losing clarity.

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?

Given no output schema and only two parameters, the description covers all necessary aspects: what the tool returns (connector id, access, audience, accounts, connect_url, caveat), important behavioral nuances (plan handling, keyword requirement, caveats), and usage context (call before connecting). It is fully actionable for an AI agent.

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?

With 0% schema description coverage, the description compensates by explaining keywords as bank name array with examples, noting it is required, and explaining include_accounts. However, it does not provide default values or edge cases for the parameters.

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 that the tool searches bank connectors by name, specifying the verb and resource. It distinguishes itself from sibling tools by focusing on searching for connectors to provide a connect URL, and mentions it should be called before connecting.

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 explicitly says 'Call this BEFORE connecting' and explains that keywords are required, returning a hint otherwise. It also guides users to prefer Open Finance connectors over credential ones with caveats. However, it does not explicitly exclude any alternative tools or give when-not-to-use conditions.

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