Skip to main content
Glama

Banco do Nordeste do Brasil 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?

Discloses that it performs a PATCH request, polls up to ~60s, returns final status fields, and handles errors like needs_action with reconnect_url. Since annotations only provide basic hints (readOnlyHint: false, destructiveHint: false), the description adds rich behavioral 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?

The description is well-organized and front-loaded, but slightly verbose. Each sentence adds value, though some redundancy exists (e.g., explaining 'without disconnecting' twice). Still highly efficient for the complexity.

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?

Despite no output schema, the description completely explains return object fields (status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url, timed_out). It also provides system context like 'UPDATE mode' and slot consumption. Perfectly adequate for agent decision-making.

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 0% description coverage, but the description fully explains both parameters: items as array of selectors (item_id, connector_id, etc.) with omission syncing all, and wait boolean with default true and fire-and-forget behavior. All parameter semantics are thoroughly defined.

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 it forces a bank to re-sync connections and waits for completion. It specifies the action (force sync), resource (one or more connections), and distinguishes it from sibling tools like openfinance_get_item_status which is for checking after timeout.

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 states when to use ('when a balance or transaction list looks stale'), what it avoids (reconnecting/disconnecting), and provides alternatives ('re-check with openfinance_get_item_status' for timeout, set wait:false for fire-and-forget).

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

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

A3.9/5.0
Disambiguation4/5

Most openfinance_* tools target a distinct resource and action, and the descriptions carefully separate overlapping endpoints like openfinance_list_transactions vs openfinance_list_transactions_by_item and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills. The main ambiguity risk is the broad marketplace mega-tool, but its many sub-capabilities are explicitly enumerated.

Naming Consistency4/5

Tool names consistently use snake_case with a strong openfinance_ prefix and verb-led patterns like list_, get_, update_, disconnect_, and force_sync. Minor deviations exist: openfinance_provider_status lacks a verb, openfinance_get_accounts_detail is awkwardly pluralized, and the platform tools (connect, marketplace, authenticate) break from the prefix pattern.

Tool Count3/5

At 25 tools, the server sits at the heavy end of the appropriate range. The Open Finance domain is complex enough to justify most entries, but the inclusion of platform-level tools like marketplace, authenticate, connect, and toolkit_info makes the overall surface feel denser and less focused than a pure banking-data server.

Completeness4/5

The set provides strong coverage of the Open Finance lifecycle: connections, sync/status, accounts, balances, transactions, credit card bills, loans, investments, category management, and provider health. Minor gaps exist, such as no dedicated investment-detail-by-id tool and no way to set custom connection labels, but these are workable and do not create critical dead ends.

Resources