Skip to main content
Glama

Dock 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 already mark the tool as read-only and idempotent. The description adds crucial behavioral details: keywords are required (returns hint if missing), caveat for non-Open-Finance connectors, plan filtering, and that it returns a ready connect_url. This goes well 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 a single, moderately long paragraph, but every sentence adds value. It front-loads the core purpose, then details returns, caveats, and plan behavior. No fluff.

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 what is returned per match (id, access, audience, connections, accounts, connect_url) and explains edge cases (caveat, plan honors). It is complete enough for an agent to use correctly.

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 description coverage is 0%, but the description fully explains both parameters: keywords with examples and required behavior, and include_accounts with its effect. This adds complete meaning beyond the bare 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 searches bank connectors by name, returns connector details, and provides a connect_url. It distinguishes from sibling tools like 'connect' by specifying it should be called before connecting to get a one-click link, making the purpose very specific and actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Call this BEFORE connecting' and explains plan behavior (PF vs PJ). It implies this is the preliminary step before using 'connect', but does not explicitly list alternatives or when not to use, so it gets a 4.

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

All Dock 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/5.0
Disambiguation4/5

Most openfinance_ tools target distinct resources (accounts, transactions, bills, loans, investments, connections, categories), so the core surface is clearly separated. However, several pairs could be confused at first glance: list_transactions vs list_transactions_by_item (both return transactions but at different scopes), get_credit_card_bill vs list_credit_card_bills (bill detail vs list of bills), and get_account_balance vs get_accounts_detail (balance snapshot vs full account object). The detailed descriptions help, but the overlap is nontrivial.

Naming Consistency4/5

The openfinance_* tools follow a consistent pattern (list_, get_, update_, search_, force_sync, provider_status, disconnect_bank), all using snake_case with a clear domain prefix. However, the general platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) have no such prefix or consistent verb_noun pattern, mixing the convention. The finance subset is strong, but the overall set isn't uniform.

Tool Count3/5

At 25 tools, this is at the upper boundary of acceptable for a broad financial domain covering connections, accounts, transactions, credit cards, loans, investments, categories, and provider health. Each tool adds real capability, so it doesn't feel bloated, but it's heavier than typical and pushes the borderline between well-scoped and too many.

Completeness4/5

The surface covers the Open Finance lifecycle thoroughly: connection management (list, reconnect, force sync, disconnect, provider status), account/balance reads, transaction listing (with filters, pagination, rich detail), credit card bills (closed and open/debt), loans, investments, category management, and a connector search. Obvious gaps like a tool for creating connections are handled via widget URLs rather than an API call, so the coverage feels adequate. Minor gaps exist (e.g., no explicit tool for updating a connection's credentials beyond reconnect URLs), but nothing that would block core workflows.

Resources