Skip to main content
Glama

Banco Sofisa 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.7/5.0
Behavior5/5

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

Describes polling behavior, timeout (~60s), return structure including status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url, timed_out. Annotations are minimal but do not contradict; description adds extensive 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with front-loaded purpose and step-by-step details. Slightly verbose but every sentence adds value.

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 input, behavior, output, and error states comprehensively. No output schema but return values are described. 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?

Both parameters (wait, items) are explained in full detail despite 0% schema coverage. Items includes valid selector types, and wait explains fire-and-forget mode.

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 the tool forces a bank re-sync and waits for completion. It distinguishes from siblings by explicitly comparing to openfinance_get_item_status and other tools for status checks versus sync initiation.

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?

Provides clear when-to-use for stale data and explains how to use wait parameter. Mentions alternative for timed_out cases but does not explicitly list when to avoid using the tool.

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

All Banco Sofisa 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.3/5.0
Disambiguation4/5

The openfinance_* tools are cleanly separated by resource and action (accounts, transactions, bills, investments, loans, connections), and the list-versus-get patterns are distinguishable. The main weak spots are the broad 'marketplace' tool, which bundles many sub-actions, and mild overlap between list_accounts/get_account_balance and list_transactions/list_transactions_by_item.

Naming Consistency4/5

The banking tools follow a consistent openfinance_<verb>_<noun> convention, with list_/get_ prefixes used predictably. A few deviations like 'provider_status' (missing a verb) and non-prefixed platform tools (authenticate, connect, marketplace, toolkit_info) keep it from being perfectly uniform.

Tool Count4/5

25 tools is on the heavy side, but the Open Finance domain justifies a wide surface: balances, transactions, bills, investments, loans, connections, sync, and provider health each need their own entry points. The platform/meta tools add some bulk but are individually useful.

Completeness5/5

The Open Finance surface covers the full read lifecycle: discover/search connectors, connect via URLs, list and inspect connections, force sync, check provider/connection status, and read accounts, balances, transactions, credit card bills, investments, and loans. It also supports the one clearly expected write operation (transaction category correction), leaving no obvious dead ends in the core domain.

Resources