Skip to main content
Glama

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Discloses waiting behavior (~60s), polling mechanism, and result fields including error states (needs_action, timed_out). Annotations only indicate non-readonly/non-destructive, but description adds crucial context.

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?

Description is long but every sentence adds value. Could be slightly more concise, but front-loads the core action and provides comprehensive details without redundancy.

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, description thoroughly explains return structure (results, errors, status fields) and error handling (reconnect_url for auth issues). Covers all user-facing aspects of the tool.

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?

Schema has 2 parameters with 0% description coverage; description compensates fully by explaining wait's effect on synchronization mode and items' flexible selectors (item_id, connector_name, etc.) and default behavior.

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 it forces a bank to re-sync connections and waits for completion. Distinguishes from sibling tools like openfinance_get_item_status by specifying it triggers a sync and returns final status.

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 describes when to use (stale balances/transactions), how to use (array of selectors or omit for all), and when not (wait: false for fire-and-forget). Mentions alternative tool for checking status if timeout.

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

All Banco BRB 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 map cleanly to distinct resources and actions, and the list/get split is readable. The main risk is openfinance_list_transactions vs openfinance_list_transactions_by_item, which both return transactions and could be confused; openfinance_get_item_status vs openfinance_provider_status also sound similar, though descriptions clarify them.

Naming Consistency4/5

The openfinance_* family follows a consistent openfinance_<verb>_<noun> pattern, and platform tools mostly use simple verb_noun names. Deviations include openfinance_list_transactions_by_item, which breaks the noun pattern, and the non-prefixed platform tools (authenticate, connect, marketplace) mixing in a second naming category.

Tool Count3/5

At 25 tools, this is at the high end of reasonable scope. The open finance data surface is genuinely broad, so most tools earn their place, but the marketplace/platform tools effectively add a second unrelated domain and push the set toward heavy.

Completeness4/5

The open finance lifecycle is well covered: connection search, sync, status, disconnect, accounts, balances, transactions, credit card bills, loans, investments, and category correction. Minor gaps exist (no single-transaction fetch, no connection update beyond force_sync), but core agent workflows do not hit dead ends.

Resources