Skip to main content
Glama

RecargaPay 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. First observed

TDQS

A5/5.0
Behavior5/5

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

The description fully discloses the behavioral profile: it PATCHes, polls up to ~60s, advances `lastUpdatedAt`, sets `synced`, reports `needs_action` with `reconnect_url`, and handles `timed_out`. Despite lacking annotations, it covers side effects, auth requirements, and operational nuances with 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 long but every sentence earns its place, covering purpose, usage, parameters, return shape, error states, and timing. It is front-loaded with the core action and progressively adds necessary detail without fluff. Structure is logical and scannable.

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's complexity (sync, polling, auth failures, reconnect flow) and the absence of an output schema, the description is exceptionally complete. It explains results, errors, status fields, actionable `needs_action` states, timeout behavior, and fallback alternatives. No critical information is missing.

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% but the description fully compensates. It explains `items` as selectors (item_id, connector_id, connector_name, custom_label) and clarifies that omitting it syncs all connections. `wait` is described as controlling blocking vs fire-and-forget. This adds substantial meaning beyond the bare schema types.

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 opens with a specific verb+resource: 'Forces the bank to re-sync one or more connections NOW and WAITS for it to finish.' It clearly distinguishes from siblings by explicitly stating 'WITHOUT disconnecting/reconnecting' and contrasting with stale reads. The scope (specific connections vs. all) is also clearly defined.

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?

Explicit when-to-use guidance is provided: 'Use this when a balance or transaction list looks stale.' It also tells when not to use it (rather than disconnecting/reconnecting) and names an alternative for timeout handling ('re-check with openfinance_get_item_status'). The `wait: false` fire-and-forget option is also clearly explained.

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

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

A3.9/5.0
Disambiguation4/5

The openfinance_* tools mostly split cleanly by resource (accounts, transactions, bills, loans, investments, connections) and action (list/get/update/force_sync), so an agent can usually pick the right one. The main ambiguity is between openfinance_list_transactions and openfinance_list_transactions_by_item, and between openfinance_get_item_status and openfinance_provider_status, but the detailed descriptions clarify those boundaries.

Naming Consistency3/5

The dominant openfinance_<verb>_<noun> pattern is clear and all names are snake_case. However, the generic tools break the convention entirely (authenticate, connect, marketplace, report_bug, show_version, toolkit_info), and openfinance_list_transactions_by_item uses an awkward extra preposition, so the naming pattern is not fully uniform.

Tool Count3/5

At exactly 25 tools, this is at the heavy end of the acceptable range. The openfinance family is comprehensive and each tool has a defined purpose, but several platform-level utilities (authenticate, connect, show_version, toolkit_info, report_bug) are administrative extras rather than core financial capabilities.

Completeness4/5

For a read-heavy Open Finance aggregation server, coverage is strong: connections, accounts, balances, transactions, bills, loans, investments, categories, sync, and status checks are all present. Write support is mostly limited to category updates plus connect/disconnect/sync, so agents cannot initiate payments or modify financial records, but that appears outside the stated scope.

Resources