Skip to main content
Glama

Caixa Tem MCP

by io.github.mcp-dir

openfinance_list_connections

Read-onlyIdempotent

Returns the saved bank connections for this install: connector_id, item_id, bank name, a per-connection reconnect_url, and an add_connection_url to link additional banks via the Open Finance widget. The reconnect_url reopens the widget in UPDATE mode for that EXISTING connection (user re-enters credentials / MFA token and the data refreshes in place) — use it when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data). It does NOT consume a connection slot and does NOT require disconnecting first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint false. The description adds useful behavioral context about the reconnect_url behavior (reopens widget in UPDATE mode) and the add_connection_url. It does not contradict annotations and goes beyond basic read-only behavior.

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 a single paragraph that packs several key pieces of information (what is returned, what each URL does). While not extremely concise, every sentence adds value and there is no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the return fields and explains the semantics of the reconnect_url and add_connection_url. With no output schema, it provides sufficient context for the agent to understand the output and usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters; schema coverage is 100%. The description adds no parameter information because none exist. However, it details the output structure, including the reconnect_url and add_connection_url, which adds value 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?

The description clearly states the tool returns saved bank connections and lists specific fields (connector_id, item_id, bank name, reconnect_url, add_connection_url). It distinguishes itself from sibling tools like connect and disconnect by explaining that reconnect_url is for re-authentication without consuming a slot.

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?

The description provides explicit guidance on when to use the reconnect_url (re-authentication, LOGIN_ERROR, stale data) and what it does not do (consume connection slot, require disconnecting). This helps the agent choose between this tool and alternatives like connect.

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