Skip to main content
Glama

Banco MCP

by io.github.douglac

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?

The description goes far beyond the sparse annotations by disclosing the polling mechanism, 60s timeout, return structure, `timed_out` flag, `needs_action` with reconnect_url, and the effect of `wait: false`. This provides complete behavioral transparency without contradicting any 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?

Although the description is longer than average, every sentence carries essential operational detail—from the immediate action to return handling, error scenarios, and sync modes. It is front-loaded with the core purpose and structured in a logical flow that avoids 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, the description thoroughly documents the response shape (`{ results, errors }`, status fields, `lastUpdatedAt`, `synced`, `reconnect_url`, `timed_out`) and error recovery. Combined with parameter semantics and usage guidance, it provides everything an agent needs to invoke and interpret 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 description coverage is 0%, but the description fully compensates: it explains `items` as an array of selectors (item_id, connector_id, connector_name, custom_label) and that omitting it syncs all. It also defines `wait: false` behavior, enriching the minimal boolean schema with actionable semantics.

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 opens with a specific verb and resource: 'Forces the bank to re-sync one or more connections NOW and WAITS for it to finish' with an explicit HTTP method and polling behavior. It clearly distinguishes from sibling tools like openfinance_get_item_status by explaining it triggers a sync rather than just reading 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?

Explicit guidance is given: 'Use this when a balance or transaction list looks stale' and it contrasts with disconnecting/reconnecting. It also instructs to check openfinance_get_item_status on timeout and explains the `wait: false` fire-and-forget alternative, covering both when and when-not scenarios.

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

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

Each tool targets a specific resource/action (balance, transactions, bills, loans, investments, connections, categories, provider status), with clear boundaries. Minor overlap exists between openfinance_list_transactions and openfinance_list_transactions_by_item, and among the multiple account-related tools, but the descriptions are detailed enough to disambiguate.

Naming Consistency4/5

Almost all tools follow an openfinance_<verb>_<noun> snake_case pattern (list_accounts, get_credit_card_bill, update_transaction_category). Minor deviations include openfinance_provider_status (noun_noun) and openfinance_list_transactions_by_item (extra preposition), but the overall convention is predictable and consistent.

Tool Count4/5

19 tools is on the heavier side but fits the broad scope of an Open Finance banking integration covering connections, accounts, transactions, credit cards, loans, investments, and provider health. Each tool appears justified; the count does not feel bloated.

Completeness5/5

The surface covers the full lifecycle: connection discovery/search/list/sync/disconnect/status, account and transaction retrieval, credit card bill summaries and detail, loans, investments, transaction categorization, and provider diagnostics. No critical dead ends are apparent for the stated banking data domain.

Resources