Skip to main content
Glama

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

A5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, etc.), description details the PATCH-then-poll behavior up to ~60s, return structure including status, executionStatus, lastUpdatedAt, synced, needs_action with reconnect_url, and timed_out behavior. Also explains wait parameter effect. No contradiction 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.

Conciseness5/5

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

Well-structured and front-loaded with core action. Every sentence adds value: use case, parameter details, error handling, alternative modes. Efficient use of text 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?

Comprehensive for a tool with no output schema: explains return format, fields, error conditions (needs_action, timed_out), and references sibling tool for follow-up. Covers edge cases and provides complete context for correct invocation.

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?

Despite 0% schema description coverage, description fully explains both parameters: items as array of selectors (item_id, connector_id, etc.) or omit for all; wait: false for fire-and-forget. Adds meaning beyond schema types.

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 re-sync of bank connections and waits for completion. Specific verb 'force_sync' and resource 'connections'. Distinguishes from siblings like openfinance_get_item_status by explaining it triggers a sync rather than just checking 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 says when to use: 'when a balance or transaction list looks stale'. Contrasts with alternatives: no need to disconnect/reconnect, and if timed_out, re-check with openfinance_get_item_status. Also explains fire-and-forget mode with wait:false.

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

All Banco Digio 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
Disambiguation4/5

Most tools map clearly to a distinct openfinance resource or action (accounts, transactions, bills, investments, loans, connections, provider health), and the platform utilities are a separate family. The only realistically confusable pairs are openfinance_list_transactions vs openfinance_list_transactions_by_item and openfinance_list_accounts vs openfinance_get_accounts_detail, but the descriptions draw sharp boundaries between them.

Naming Consistency4/5

The 19 openfinance_* tools follow a strong openfinance_<verb>_<noun> convention, with only minor exceptions like openfinance_provider_status and openfinance_list_transactions_by_item. The six platform tools mix bare verbs (authenticate, connect), nouns (marketplace, toolkit_info), and verb_noun (report_bug, show_version), but they are clearly a separate utility layer.

Tool Count3/5

25 tools sits at the top of the 'feels heavy' band. The number is defensible for a full Open Finance data product plus platform management tools, but an agent is exposed to a lot of surface area, and the same server mixes a banking-data adapter with a marketplace/utility layer.

Completeness5/5

The openfinance surface covers the full lifecycle: search/connect/reconnect/disconnect banks, force-sync, item status, provider incidents, accounts, balances, transactions per account and per connection, credit-card bills with paid-status derivation, investments and investment transactions, loans, loan detail, and transaction categorization. Platform tools cover auth, connection status, toolkit state, version, bug reporting, and marketplace operations, so there are no obvious dead ends.

Resources