Skip to main content
Glama

Banco Bmg MCP

by io.github.mcp-dir

openfinance_force_sync

Forces the bank to re-sync one or more connections NOW and WAITS for it to finish (PATCH /items/:id, then polls until the item stops updating, up to ~60s). Use this when a balance or transaction list looks stale: a connection can read UPDATED yet be hours old, and this pulls fresh data WITHOUT disconnecting/reconnecting. Pass items as an array of selectors (item_id, connector_id, connector_name, or the user-set custom_label nickname); OMIT items to sync ALL linked banks. Returns { results, errors }; each result has the final status, executionStatus, lastUpdatedAt (advances when data is refreshed), and synced (true = fresh data is ready). needs_action (e.g. MFA_REINTERACTION / LOGIN_ERROR / WAITING_USER_INPUT) means the user must re-authenticate — those results include a reconnect_url that opens the widget in UPDATE mode for that exact connection (user enters credentials / MFA token, data refreshes in place, no slot consumed, no disconnect needed). timed_out: true means the sync is still running — re-check with openfinance_get_item_status. Set wait: false for fire-and-forget (returns immediately while UPDATING).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNo
itemsNo

TDQS

A4.9/5.0
Behavior5/5

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

Adds rich behavioral details beyond annotations: polling up to 60s, return format with final status, synced flag, needs_action with reconnect_url, timed_out fallback. Annotations are minimal and not contradicted.

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?

Single paragraph is well-organized and front-loaded but could be slightly more structured with bullet points. Still very effective and efficient.

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?

Covers all aspects: purpose, usage, parameters, return values, error handling, edge cases, and interaction with other tools. No output schema, but description fully compensates.

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

Parameters5/5

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

Both parameters are thoroughly described despite 0% schema coverage. Items explained as array of selectors and optional meaning sync all; wait explained as true/false with fire-and-forget semantics.

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?

Clearly states the tool forces a sync of connections and waits for completion. Distinguishes from siblings by focusing on force re-sync vs. other actions like get status or list.

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?

Explicitly says when to use (stale balances/transactions) and what it does not do (disconnect/reconnect). Provides guidance on items and wait parameters and handling of needs_action results.

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