Skip to main content
Glama

EQI 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. Added
  8. Removed
  9. Added
  10. Removed
  11. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate mutation (readOnlyHint=false), non-destructive (destructiveHint=false), non-idempotent (idempotentHint=false). Description adds extensive context: PATCH then polls up to ~60s, explains needs_action with reconnect_url, timed_out behavior, and return fields. No contradiction.

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?

Description is thorough but slightly long. However, it is well-structured: core action first, then parameters, return format, edge cases. Every sentence adds value. Minor room for trimming but overall effective.

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 complexity (polling, multiple outcomes, no output schema), the description is very complete. It covers all aspects: sync behavior, parameter meaning, return fields, error states (needs_action, timed_out), and alternatives. No gaps.

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 has 2 params (wait boolean, items array of strings) with 0% description coverage. Description fully compensates: items can be selectors (item_id, connector_id, etc.) or omitted for all; wait defaults to true (implied) and false for fire-and-forget. Explains implications of each parameter.

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 distinguishes from sibling tools like openfinance_get_item_status (re-check) and openfinance_disconnect_bank (disconnect/reconnect). Verb 'forces' and resource 'bank connections' are specific and unambiguous.

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 (stale balance/transactions) and when not (disconnect/reconnect not needed). Provides guidance on omitting items to sync all, and setting wait: false for fire-and-forget. Also mentions alternative tool openfinance_get_item_status for timed_out cases.

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

All EQI 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

The openfinance_* tools are clearly separated by resource and action, and their detailed descriptions make most choices unambiguous. However, marketplace is a multi-action mega-tool that duplicates report_bug, and openfinance_list_transactions vs openfinance_list_transactions_by_item have some overlap that could cause misselection.

Naming Consistency4/5

The 19 openfinance_* tools follow a consistent and predictable 'openfinance_<verb>_<noun>' pattern. The non-openfinance tools are a mixed set (marketplace, toolkit_info, show_version, report_bug, authenticate, connect), which is readable but not fully uniform.

Tool Count3/5

25 tools lands right at the heavy end of the borderline range. The Open Finance domain genuinely has many distinct resources, but the marketplace tool alone packs in many sub-actions, which makes the total tool count feel more bloated than the domain strictly requires.

Completeness4/5

The surface covers the full Open Finance lifecycle well: connections, sync/disconnect, accounts, transactions, credit card bills, loans, investments, categories, provider health, and platform administration. Minor gaps exist, such as no direct connect/add-bank tool beyond returning a connect_url and no get-single-transaction endpoint, but agents can work around these.

Resources