Skip to main content
Glama

Caixa Econômica Federal 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

A5/5.0
Behavior5/5

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

Discloses the PATCH operation, polling up to 60s, and return fields like status, synced, timed_out. Explains that syncing does not disconnect/reconnect. Annotations only provide basic safety hints, but the description adds rich behavioral 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence is necessary and informative. It is well-structured: core purpose first, then usage guidance, parameter details, and return value explanation. No wasted words.

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, the description thoroughly covers return values and possible states (synced, timed_out, needs_action). It also covers both parameters comprehensively. The tool is complex, and the description is complete enough for correct invocation and interpretation.

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, the description fully explains both parameters: 'items' is an array of selectors (item_id, etc.) or omitted for all banks; 'wait' is a boolean for synchronous vs fire-and-forget behavior. This adds critical meaning absent from the 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?

The description clearly states the tool forces a re-sync of connections and waits for completion. It specifies the resource (connections), the action (force sync), and distinguishes from alternatives by noting it pulls fresh data without disconnecting.

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 states when to use: when balance or transaction list looks stale. Provides guidance on results: 'needs_action' leads to reconnect_url, 'timed_out' suggests re-checking with another tool. Also explains the 'wait' parameter for fire-and-forget usage.

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

All Caixa Econômica Federal 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.2/5.0
Disambiguation4/5

Most tools have distinct purposes, especially with the openfinance_ prefix grouping banking operations. However, pairs like openfinance_list_accounts vs openfinance_get_accounts_detail and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills could cause minor confusion, though descriptions help.

Naming Consistency5/5

Tools consistently use snake_case with a clear verb_noun pattern. Open finance tools all start with openfinance_, and utility tools use simple verbs like authenticate, connect, report_bug. No mixing of conventions.

Tool Count3/5

At 24 tools, the count is on the higher side of the borderline range. The server combines platform management (6 tools) and banking operations (18 tools), which justifies the number, but it feels slightly heavy for a single server.

Completeness5/5

The tool surface covers all major banking operations (accounts, transactions, credit cards, investments, loans) and includes essential maintenance tools (sync, status, disconnect, search connectors). Platform management is also comprehensive with authentication, marketplace operations, and diagnostics.

Resources