Skip to main content
Glama

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

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

Discloses polling up to ~60s, fire-and-forget option, return fields (status, executionStatus, etc.), error states (needs_action with reconnect_url), and timed_out behavior. Adds significant context beyond annotations.

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?

Well-structured and front-loaded, but slightly verbose. Every sentence adds value, though could be tightened slightly without losing information.

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?

Comprehensive for a sync tool: covers async behavior, error handling, return format, and cross-reference to get_item_status. No output schema exists, but description covers all needed info.

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 coverage, description fully explains both parameters: 'items' as array of selectors (including omission for all banks) and 'wait' for fire-and-forget. No ambiguity.

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?

Clearly states the verb 'Forces re-sync' and resource 'one or more connections', with explicit behavior of waiting or fire-and-forget. Distinguishes from siblings like get_item_status and list_connections.

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?

Explicitly says when to use: 'when a balance or transaction list looks stale'. Mentions alternative for timed_out results. Could be improved with explicit when-not-to-use, but sufficient.

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

All Woop 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.7/5.0
Disambiguation3/5

Several tools have overlapping purviews—list_transactions vs list_transactions_by_item, get_credit_card_bill vs list_credit_card_bills, and connect vs list_connections vs get_item_status vs provider_status—so an agent could pick the wrong one. The very detailed descriptions disambiguate them, but the tool names alone do not.

Naming Consistency3/5

The openfinance_ prefix provides a clear family and most members use list_/get_/update_ verbs, but there are deviations like openfinance_provider_status (no verb), openfinance_disconnect_bank, and openfinance_force_sync. Platform tools (authenticate, connect, marketplace, toolkit_info) follow a different, less uniform style.

Tool Count3/5

At 25 tools, this sits at the top of the heavy range. Most Open Finance operations are justified given the breadth of banking data, but overlapping tools and the mega-marketplace tool with many sub-actions make the set feel slightly bloated.

Completeness5/5

The Open Finance surface covers list/get/update/disconnect/sync for accounts, transactions, credit card bills, loans, and investments, plus provider health, connection search, and platform-level auth, marketplace, version, and feedback. There are no obvious dead ends or missing lifecycle operations.

Resources