Skip to main content
Glama

QI SCD 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. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations provide only basic hints. The description adds rich behavioral detail: polling up to ~60s, response structure (results, errors, status fields), handling of re-authentication needs (reconnect_url), and timeout behavior. This fully compensates for lack of annotation detail.

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 comprehensive yet well-organized: purpose, usage, parameter details, return value, error states, and wait option. Every sentence adds value; no fluff. It is appropriately front-loaded with the core action.

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 fully explains the return format, including result fields and error conditions (needs_action, timed_out). All 2 parameters are thoroughly documented. The tool's behavior and edge cases are covered, making it complete for agent 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?

Schema has 2 parameters with 0% coverage; description explains both in depth: 'wait' defaults to true and can be set false for fire-and-forget; 'items' is an array of selectors (item_id, connector_name, etc.) and omitting it syncs all. This adds crucial meaning beyond the schema.

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 re-sync of bank connections and waits for completion. It distinguishes from sibling tools like openfinance_get_item_status (re-check) by specifying that this triggers a sync. The verb 'forces' and resource '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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use ('when a balance or transaction list looks stale') and provides context on wait behavior (fire-and-forget vs. wait). It also hints at alternatives (re-check with openfinance_get_item_status on timeout). However, it does not explicitly state when not to use or compare to other sync tools, missing some exclusion guidance.

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

All QI SCD 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.2/5.0
Disambiguation4/5

Most tools are clearly distinct, especially within the openfinance_* group, with detailed descriptions covering specific resources and actions. Minor overlap exists between list_transactions and list_transactions_by_item, and between get_credit_card_bill and list_credit_card_bills, but the descriptions clearly delineate their use cases (per-account vs whole-connection, detail vs summary).

Naming Consistency4/5

The openfinance_* tools consistently follow a verb_noun pattern (e.g., list_accounts, get_item_status, update_transaction_category), with the exception of openfinance_provider_status which uses a noun phrase. Non-openfinance tools like authenticate, connect, marketplace, and report_bug are less uniform but still readable. Overall, the convention is mostly consistent.

Tool Count4/5

At 25 tools, this is on the higher end but justified by the comprehensive Open Finance domain covering accounts, transactions, credit cards, loans, investments, connections, categories, and provider status. Each tool serves a specific operation, and the marketplace and platform utilities round out the surface. It's slightly heavy but not excessive.

Completeness5/5

The tool surface covers the full lifecycle for Open Finance data: listing and detailing accounts, retrieving balances, managing transactions (including categorization), handling credit card bills (list and detail with transactions), loans, investments, and connection health (sync, status, disconnect, search). Also includes authentication, marketplace, and utility tools. No obvious gaps for the stated purpose.

Resources