Skip to main content
Glama

Caixa Tem MCP

by io.github.mcp-dir

openfinance_search_bank_connectors

Read-onlyIdempotent

Searches the available bank connectors by name (pass keywords[], e.g. ['nubank','btg']) and returns, per match: the connector id, whether it's Open Finance or API (access), PF/PJ (audience), the user's already-linked connections (and accounts when include_accounts=true), and a ready connect_url with the bank pre-selected. Some non-Open-Finance credential connectors carry a caveat warning that they don't auto-update (needs periodic manual reconnection) — surface it so the user can prefer the institution's Open Finance connector for automation. Honors the user's plan (a PF plan hides PJ banks; a PJ plan covers BOTH — PF and PJ banks connect and count under the same plan). Call this BEFORE connecting to hand the user a one-click link to the right bank. keywords[] is REQUIRED — without it returns a hint (never dumps the whole catalog).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNo
include_accountsNo

TDQS

A4.8/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral details: returns connect_url, honors user plan, handles caveats, and never dumps full catalog. 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 dense and informative, front-loading purpose and output. It could be slightly more concise, but every sentence adds value and the structure is logical. No wasted words.

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?

Given no output schema, the description adequately explains return fields (id, access, audience, connections, accounts, connect_url) and behaviors (plan, caveat). Minor omissions: no explicit mention of empty result handling, but overall complete for a search tool.

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 description fully explains both parameters: keywords (required for search, with example) and include_accounts (adds accounts to returned data). The description compensates completely for the missing schema descriptions.

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 searches bank connectors by name, specifying the action ('searches'), resource ('bank connectors'), and parameters (keywords). It details the returned fields and distinguishes itself from sibling tools like 'connect' and 'marketplace' by positioning itself as a preliminary search step.

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 instructs to call before connecting, explains when to surface caveat warnings, and clarifies that keywords are required and returns a hint otherwise. It also mentions plan implications (PF vs PJ), giving clear guidance on usage context.

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