Skip to main content
Glama

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

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

Discloses waiting behavior (up to ~60s), return shape (results, errors), error conditions (needs_action, timed_out), and reconnection flow. Adds context beyond annotations, which only mark readOnlyHint=false.

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 thorough and well-structured, front-loading key behavior. Slightly verbose but every sentence adds value; minor improvements could trim redundancy.

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 no output schema, description comprehensively covers return fields (status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url, timed_out). All necessary context for a complex sync tool is provided.

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, description fully explains both parameters: wait (fire-and-forget option) and items (array of selectors or omit for all). Meaning is clearly conveyed.

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 action: force a re-sync of connections and wait for completion. It specifies the resource (connections) and distinguishes from siblings by mentioning no disconnect needed.

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?

Explicitly tells when to use (stale balance/transactions), what it does (pulls fresh data without disconnecting), and provides alternatives like fire-and-forget with wait: false.

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

All Sicoob 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
Disambiguation4/5

Most openfinance_* tools target clearly distinct resources (accounts, transactions, bills, loans, investments, connections, categories). Minor overlap exists—list_accounts returns balances and list_transactions_by_item consolidates what list_transactions provides—but the detailed descriptions distinguish them adequately.

Naming Consistency4/5

The openfinance_* tools follow a consistent verb_noun pattern (get_*, list_*, update_*, force_sync, search_*) with one slight deviation: openfinance_provider_status omits a verb. The non-openfinance platform tools (authenticate, connect, marketplace, report_bug, etc.) break the prefix pattern, creating two naming conventions within the same server.

Tool Count3/5

25 tools sits at the upper boundary of acceptable for a comprehensive Open Finance banking adapter, covering accounts, transactions, credit cards, loans, investments, and connection management. However, including meta-platform tools like marketplace and toolkit_info inflates the count and makes the set feel heavier than a pure banking tool surface.

Completeness4/5

The tool surface covers the core Open Finance lifecycle well: list/get accounts, balances, transactions, credit card bills, loans, investments, connection management, category correction, and provider status. Gaps include no direct new-bank connection tool (only URLs) and no investment detail endpoint beyond transactions, but agents can work around these.

Resources