Skip to main content
Glama

Íon 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. Added
  4. Removed
  5. Added
  6. Removed
  7. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description fully discloses behavioral traits: it waits up to ~60s with polling, returns specific fields (final status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url), and covers error conditions like MFA_REINTERACTION. The annotations are minimal, so the description carries the full burden and does so thoroughly.

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?

The description is information-dense yet well-structured. Every sentence adds value: purpose, usage context, parameter semantics, return values, error handling, and timeout behavior. It is appropriately sized for the tool's 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?

Given 2 parameters, no output schema, and the complexity of a sync operation with polling, the description covers all necessary aspects: what it does, when to use, how to use parameters, what to expect in the response, and how to handle errors (needs_action and reconnect_url). It is comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter schema has 0% description coverage, but the description compensates by explaining the items parameter (array of selectors: item_id, connector_id, etc., and omitting syncs all) and the wait parameter (default behavior and fire-and-forget option). It could be more explicit about the default value of wait, but overall it adds significant semantic value.

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 re-sync of one or more connections and waits for completion. It uses a specific verb ('forces') and resource ('connections'), and distinguishes from sibling tools like openfinance_get_item_status (for checking status) and openfinance_disconnect_bank (for disconnecting).

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?

The description explicitly says when to use it ('when a balance or transaction list looks stale') and clarifies it pulls fresh data without disconnecting. It also explains the wait parameter (true by default, false for fire-and-forget) and mentions re-checking with openfinance_get_item_status if timed_out. However, it does not explicitly list cases where the tool should not be used, which would improve clarity further.

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

All Íon 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
Disambiguation5/5

Each openfinance tool targets a distinct resource/operation (accounts, transactions, bills, loans, investments, connections, categories, sync, status), and the non-openfinance tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) are clearly separate. The only near-overlap is between openfinance_list_transactions and openfinance_list_transactions_by_item, but the latter explicitly handles whole-connection consolidation and the descriptions clarify when to use each.

Naming Consistency5/5

All openfinance tools share the `openfinance_` prefix with a consistent verb_noun pattern (list_, get_, update_, force_sync, provider_status, search_). Non-openfinance tools use simple imperative verbs (authenticate, connect, report_bug, show_version) and the noun-phrase toolkit_info, all consistent in style with no mixed conventions.

Tool Count4/5

25 tools is on the high side, but each serves a distinct function within the comprehensive Open Finance domain (accounts, transactions, bills, loans, investments, connections, categories, sync, status) plus general server utilities. The count is justified by the breadth of the domain, though it exceeds the typical 3-15 range.

Completeness4/5

The surface covers the full read lifecycle for financial data: listing and detail for accounts, transactions, bills, loans, investments, plus connection management (list, disconnect, force_sync), categories, and provider status. Missing write operations like transfers are likely out of scope, and minor gaps such as no separate 'get investment' detail are acceptable since list_investments returns comprehensive data.

Resources