Skip to main content
Glama

Rede Celcoin 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. Added
  12. Removed
  13. Added
  14. Removed
  15. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description goes beyond annotations to detail behavioral traits: waits up to ~60s, returns specific status fields, handles errors like MFA with reconnect_url, and explains needs_action. No contradiction with 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?

The description is informative but relatively long. It is front-loaded with key purpose and all sentences add value. Slightly longer than necessary but still clear.

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 absence of output schema and the complexity of the tool (sync with polling, error states, reconnect_url), the description is complete. It covers return structure, timeout handling, and references sibling tools appropriately.

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 explains both parameters: items (array of selectors or omit for all) and wait (false for fire-and-forget). Adds meaning beyond 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 clearly states the tool forces a re-sync of bank connections and waits for completion. It uses specific verbs ('forces sync') and identifies the resource ('connections'). It distinguishes from siblings like openfinance_get_item_status by mentioning it as a fallback for timeout.

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 guidance on when to use the tool (stale balance/transactions) and what it does (pulls fresh data without disconnecting). It also explains alternatives: set wait:false for fire-and-forget and re-check with openfinance_get_item_status on timeout.

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

All Rede Celcoin 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
Disambiguation3/5

Most openfinance_* tools target distinct resources and actions, but several overlap in purpose: list_transactions vs list_transactions_by_item, get_credit_card_bill vs list_credit_card_bills, and multiple connection/status tools expose reconnect URLs. The long descriptions help, but the boundaries are not always immediately obvious.

Naming Consistency4/5

The openfinance_* tools follow a consistent list_/get_ verb_noun pattern and share a clear prefix. The smaller platform cluster is less consistent — marketplace, connect, authenticate, show_version, toolkit_info — mixing nouns, bare verbs, and snake_case, but it is a minor deviation overall.

Tool Count3/5

At 25 tools, this sits at the heavy end of acceptable. The Open Finance surface is broad enough to justify many of them, but there is redundancy (e.g. list_transactions_by_item largely wraps list_transactions plus account resolution) and a separate platform-management cluster that makes the set feel sprawling.

Completeness4/5

The Open Finance domain is well covered: connection lifecycle, accounts, balances, transactions, credit-card bills, loans, investments, categories, and provider status are all present, and data flows connect properly between tools. Minor gaps exist, such as no single-transaction fetch or dedicated prompt-management tools, but the marketplace tool fills those roles.

Resources