Skip to main content
Glama

Banrisul 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. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Despite annotations being minimal (readOnlyHint false, destructiveHint false, etc.), the description thoroughly explains behavior: polling up to ~60s, possible final statuses (status, executionStatus, lastUpdatedAt, synced), needs_action with reconnect_url, and timed_out. No contradictions with annotations.

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 a single, dense paragraph but every sentence adds value. It is front-loaded with the main action and timeout. Could be slightly more structured (e.g., bullet points), but not overly verbose.

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 the tool's complexity (2 parameters, no output schema), the description covers purpose, usage, parameters, return format, error handling, and alternative tools. It is fully self-contained.

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?

The schema has 2 parameters with 0% coverage, but the description fully explains them: 'wait' boolean (fire-and-forget when false) and 'items' array (selectors or omit for all). This compensates completely for the schema's lack of descriptions.

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 uses specific verbs like 'forces re-sync' and 'pulls fresh data', and distinguishes itself from siblings by indicating it is for stale data without disconnecting.

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?

The description explicitly tells when to use the tool ('when a balance or transaction list looks stale'), how to sync all (omit items), and how to handle errors (needs_action with reconnect_url). It also mentions alternatives like openfinance_get_item_status for timeout cases.

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

All Banrisul 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.2/5.0
Disambiguation5/5

Each tool targets a distinct resource or action (e.g., accounts, transactions, loans, investments, credit card bills, connection status, provider status, sync, marketplace, authentication). Descriptions are highly detailed, making overlaps virtually nonexistent. The only potential overlap (openfinance_list_transactions vs. openfinance_list_transactions_by_item) is resolved by the latter being a consolidated analysis tool for a whole connection.

Naming Consistency5/5

All tools follow a consistent snake_case pattern. Open Finance tools are uniformly prefixed with 'openfinance_' and follow a clear verb_noun structure (e.g., openfinance_list_accounts, openfinance_get_account_balance). Non-Open-Finance tools (authenticate, connect, marketplace, etc.) also use simple, predictable verb names. No mix of conventions.

Tool Count4/5

With 25 tools, the count is on the higher side but justified by the comprehensive scope covering Open Finance banking data, marketplace, and utility functions. The domain requires many endpoints (accounts, transactions, loans, investments, credit card bills, sync, etc.). A slight redundancy exists (e.g., two transaction listing tools), but they serve distinct use cases. The count is well-scoped for the complexity.

Completeness4/5

The tool set provides excellent read coverage for accounts, transactions, loans, investments, and credit cards, plus write support for category updates and sync forcing. Missing are tools for directly creating or deleting connections (though search provides connect_url and disconnect exists) and for managing MCPs beyond the marketplace. No critical gaps that would cause agent failures, as the core data retrieval and category correction are covered. Minor gaps exist in write operations and connection lifecycle management.

Resources