Skip to main content
Glama

Caixa Tem 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

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), polling mechanism, return statuses, MFA handling with reconnect_url, and that it does not disconnect/reconnect. No contradiction with annotations (readOnlyHint=false, destructiveHint=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?

Description is detailed but well-structured, with key action and wait behavior front-loaded. Slightly long but each sentence adds value; could be more concise without losing clarity.

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?

For a tool with no output schema, description covers output format (results, errors, synced, etc.), error states (MFA, timeout), and reconnection guidance. Comprehensive for the tool's complexity.

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?

Despite 0% schema coverage, description fully explains both parameters: items as array of selectors (item_id, connector_id, etc.) and wait as boolean for fire-and-forget mode, adding essential meaning beyond 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?

Description explicitly states the tool forces bank re-sync, waits for completion, and returns results. Clearly differentiates from sibling tools like openfinance_get_item_status and alternatives like disconnect/reconnect.

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 when-to-use guidance ('balance or transaction list looks stale'), how to use (pass items array or omit for all), and alternatives (fire-and-forget with wait:false, 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 Caixa Tem 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.8/5.0
Disambiguation3/5

The openfinance_* tools are mostly distinct, but several have overlapping boundaries: openfinance_list_transactions vs openfinance_list_transactions_by_item, openfinance_get_item_status vs openfinance_provider_status, and openfinance_list_accounts carrying balance vs openfinance_get_account_balance. The platform-level tools also blur somewhat: marketplace, toolkit_info, and connect all touch installed or available services.

Naming Consistency3/5

The openfinance_* group follows a consistent list/get/update verb pattern in snake_case, but platform-level tools like authenticate, connect, marketplace, report_bug, show_version, and toolkit_info break that convention. The set is readable, but it is split between two clearly different naming styles.

Tool Count3/5

At 25 tools, the server is at the heavy end, and several are platform/MCP-management helpers rather than core banking capabilities. The count is not absurd for a broad Open Finance + marketplace adapter, but it feels more cluttered than a focused financial data toolset should be.

Completeness4/5

The Open Finance surface is thorough: accounts, transactions, balances, credit card bills, loans, investments, connection lifecycle, sync, provider status, and category correction are all covered. The main gaps are the absence of a direct connect/create action (only URLs are returned) and no write operations beyond category updates, but for a read-centric financial data adapter this is close to complete.

Resources