Skip to main content
Glama

Banco Bmg MCP

by io.github.mcp-dir

openfinance_list_connections

Read-onlyIdempotent

Returns the saved bank connections for this install: connector_id, item_id, bank name, a per-connection reconnect_url, and an add_connection_url to link additional banks via the Open Finance widget. The reconnect_url reopens the widget in UPDATE mode for that EXISTING connection (user re-enters credentials / MFA token and the data refreshes in place) — use it when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data). It does NOT consume a connection slot and does NOT require disconnecting first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds value by explaining that reconnect_url does not consume a slot and does not require disconnection, which is useful behavioral detail.

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?

Two sentences, no wasted words. First sentence states purpose and outputs; second adds critical usage detail. Efficient and front-loaded.

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?

For a zero-parameter, list-only tool with no output schema, the description adequately explains return fields and key behavior. Could mention if any default filtering applies, but overall complete enough.

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?

No parameters exist, so the description is not required to explain them. Schema coverage is 100%, so baseline of 4 is appropriate.

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 uses a specific verb 'Returns' and names the resource 'saved bank connections', listing exact fields. It clearly distinguishes from sibling tools like openfinance_list_accounts.

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?

It explicitly describes when to use the reconnect_url (for re-authentication), but does not provide comprehensive guidance on when to use this tool vs. alternatives. Context is clear but lacks exclusions.

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

All Banco Bmg 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.1/5.0
Disambiguation3/5

The openfinance_ tools are mostly distinct by resource/action, but there are several overlapping pairs: list_accounts vs get_accounts_detail, list_credit_card_bills vs get_credit_card_bill, list_transactions vs list_transactions_by_item, and connect vs toolkit_info vs openfinance_list_connections. The descriptions help disambiguate, but an agent could still misselect between these related tools.

Naming Consistency4/5

The core banking tools consistently follow an openfinance_<verb>_<noun> pattern, which is a strong and readable convention. The generic platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break that pattern and use mixed naming styles, creating two distinct naming tiers within the same server.

Tool Count3/5

25 tools sits at the upper borderline of what feels reasonable for one server. The Open Finance domain justifies many read/query tools, but the inclusion of platform meta-tools like marketplace, connect, toolkit_info, report_bug, and show_version inflates the count beyond a tightly focused bank-data scope.

Completeness4/5

The Open Finance surface is largely complete: connectors, sync, disconnect, accounts, balances, transactions, categorization, credit card bills, loans, investments, and provider status are all covered. Minor gaps exist, such as the lack of a dedicated investment detail endpoint and limited consent/permission introspection, but agents can work around these with the existing tools.

Resources