Skip to main content
Glama

Next 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

A5/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it mentions the tool waits and polls up to ~60s, describes the return format including edge cases like 'needs_action' and 'timed_out', and clarifies that it does not disconnect/reconnect. Annotations (readOnlyHint=false, destructiveHint=false) are consistent with this, so 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.

Conciseness5/5

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

The description is front-loaded with the core action and then provides necessary details in a logical order. Every sentence adds value, and it is concise given the complexity of the tool. No unnecessary words.

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 the tool has 2 parameters and no output schema, the description covers return format, edge cases (needs_action, timed_out), and behavioral details. It is complete and leaves no ambiguity about what the tool does and how to use it.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters: 'wait' (boolean, default behavior and fire-and-forget) and 'items' (array of selectors, omitting syncs all). This provides clear 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 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 and resource, and the behavior is distinctly described, differentiating it from sibling tools like openfinance_get_item_status which is for checking 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?

The description explicitly states when to use this tool: 'Use this when a balance or transaction list looks stale'. It also mentions when not to use it (no need to disconnect/reconnect) and provides an alternative for fire-and-forget using 'wait: false'. It even suggests re-checking with openfinance_get_item_status if timed out.

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

All Next 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 tools are largely distinct, especially the openfinance_* suite which follows clear resource+action patterns. A few could be confused (e.g., openfinance_list_transactions vs openfinance_list_transactions_by_item, or get_account_balance vs list_accounts) but descriptions are thorough and clarify boundaries. The non-prefixed tools (authenticate, connect, marketplace) are also distinct, though 'marketplace' is quite overloaded internally.

Naming Consistency4/5

The openfinance_* tools follow a very consistent verb_noun pattern (list, get, force_sync, update, search, provider_status). However, the platform tools are heterogeneous: authenticate, connect, report_bug, show_version are verb_noun, but 'marketplace' and 'toolkit_info' are nouns. This mix is a minor inconsistency, but overall the naming is predictable across the two clear groups.

Tool Count4/5

At 25 tools, this is on the heavy side (16-25 is considered heavy), but the breadth is justified by a comprehensive Open Finance API (19 tools) plus platform management (6 tools). Each openfinance_* tool maps to a specific endpoint or operation, so none feel redundant. Slightly above the ideal 3-15 range, but appropriate for a full financial data adapter.

Completeness5/5

The Open Finance surface is remarkably complete: accounts, transactions, bills, loans, investments, categories, connection management (list, force_sync, status, provider_status, search connectors, disconnect), and even a categorization update. The platform side covers authentication, connectivity, marketplace operations (search/describe/invoke/install/subscribe), bug reporting, version, and toolkit info. No obvious dead ends or missing lifecycle steps.

Resources