Skip to main content
Glama

Clear 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?

Annotations are sparse (readOnlyHint=false, no idempotent/destructive hints), so the description carries the full burden. It discloses blocking behavior ('WAITS for it to finish', '~60s'), polling, timeout semantics, and the `needs_action` re-authentication flow with reconnect_url — rich, actionable context.

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 long but dense — every sentence earns its place: action, use-case, parameter details, response format, error states, and timeout behavior. It is well-structured and front-loaded, with no filler or repetition.

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?

With no output schema and minimal annotations, the description alone provides a complete picture: return shape (`results`, `errors`, `status`, `executionStatus`, `lastUpdatedAt`, `synced`), `needs_action` handling, `timed_out` behavior, and polling mechanics. It is self-contained for correct 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 offers 0% description coverage for its 2 parameters. The description compensates fully by explaining `items` accepts item_id/connector_id/connector_name/custom_label selectors and may be omitted to sync all. It also clarifies `wait: false` for async invocation, going beyond the bare 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?

Description uses a specific verb ('Forces the bank to re-sync') and identifies the exact resource ('connections'), with a clear distinction from sibling tools like list/status tools. It anchors the purpose with the underlying API call (PATCH /items/:id) and polling behavior.

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?

Provides explicit when-to-use guidance ('Use this when a balance or transaction list looks stale') and contrasts with alternatives by noting it works 'WITHOUT disconnecting/reconnecting' and directs users to openfinance_get_item_status for ongoing syncs. Also explains the `wait: false` fire-and-forget case.

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

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

Tools are mostly distinct, with clear descriptions differentiating them. Some overlap between openfinance_list_accounts and openfinance_get_accounts_detail, but descriptions clarify that one returns summaries and the other full details. The marketplace tool is very detailed and avoids confusion with Open Finance tools.

Naming Consistency3/5

The Open Finance tools follow a consistent openfinance_verb_noun pattern, but other tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) do not use a prefix. This mix of conventions reduces overall consistency, though within the Open Finance subset the pattern is clear.

Tool Count4/5

24 tools is a reasonable count for a platform covering authentication, marketplace, and detailed Open Finance operations. The number is slightly high but each tool has a clear purpose and none seem redundant.

Completeness5/5

The tool set covers the full lifecycle of bank connections: listing accounts, transactions, credit card bills, investments, loans, force syncing, provider status, and category management. The marketplace tool also allows extending functionality. No obvious gaps for the intended financial data domain.

Resources