Skip to main content
Glama

Inter 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.7/5.0
Behavior5/5

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

Annotations are minimal (no readOnly, destructive, or idempotent hints). The description richly details behavior: polls up to ~60s, fire-and-forget with wait:false, return fields (status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url, timed_out), and error handling. 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.

Conciseness4/5

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

The description is a single dense paragraph, but it is front-loaded with the core action and adds essential details. Every sentence adds value, though it could be slightly more structured (e.g., separate sections for parameters and return values). Not overly verbose.

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?

Despite lacking an output schema and having simple parameters, the description covers purpose, usage, parameters, return value semantics, error states (needs_action, timed_out), and even an alternative usage (wait:false). It is comprehensive for a tool of this complexity.

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 coverage is 0%, so the description carries full burden. It thoroughly explains both parameters: 'wait' as fire-and-forget vs. wait, and 'items' as an array of selectors (item_id, connector_id, connector_name, custom_label) with omission syncing all. No parameter is left undocumented.

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 explicitly states the tool's purpose: 'Forces the bank to re-sync one or more connections NOW and WAITS for it to finish'. It uses a specific verb (force, sync) and resource (connections), and distinguishes from siblings by explaining it avoids disconnecting/reconnecting.

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?

Provides clear when-to-use guidance: 'Use this when a balance or transaction list looks stale'. It also explains what it avoids and gives a fire-and-forget option. However, it does not explicitly state when not to use or compare to specific sibling tools.

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

All Inter 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/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: the openfinance_* family cleanly separates accounts, transactions, bills, loans, investments, connections, sync, and provider health, while platform tools (authenticate, connect, marketplace, toolkit_info) cover different concerns. Even potentially similar pairs like get_item_status vs provider_status and list_transactions vs list_transactions_by_item are clearly differentiated by their descriptions.

Naming Consistency4/5

Open Finance tools follow a uniform openfinance_<verb>_<noun> snake_case pattern, and the generic tools are also readable English verbs/nouns (authenticate, connect, report_bug). The main inconsistency is that a few generic tools are bare nouns (marketplace, toolkit_info) while the rest are verbs, but the mix is predictable and never confusing.

Tool Count3/5

25 tools sit at the upper boundary of what is comfortable, and the set spans two distinct domains (Open Finance data access plus MCP platform/marketplace management). Each tool does appear to earn its place, but the count is heavy enough to feel borderline rather than optimally scoped.

Completeness5/5

The Open Finance surface is thorough: list/get for accounts, transactions, bills, loans, and investments, with sync, connection health, provider status, category correction, and disconnect all covered. The platform side also covers authentication, connection status, marketplace discovery/invocation, bug reporting, and version info, leaving no obvious dead ends for the stated purpose.

Resources