Skip to main content
Glama

ASA 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.7/5.0
Behavior5/5

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

The description reveals non-obvious behaviors: plan-based filtering (PF hides PJ), caveat warnings for non-Open-Finance connectors, and that keywords are required. Annotations already mark it as read-only and idempotent, so description adds valuable context without contradiction.

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, dense paragraph that conveys all necessary information without fluff. It could be slightly more structured (e.g., separated notes), but every sentence earns its place.

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 the tool's moderate complexity (2 params, plan handling, caveats, no output schema), the description covers return fields, usage flow, and edge cases (empty keywords, plan types). 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?

The input schema has 0% description coverage, but the description compensates by explaining that keywords[] is required and provides example usage, and include_accounts triggers account details. This adds critical meaning beyond the bare schema structure.

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 and returns specific fields (id, access, audience, connections, connect_url). It differentiates from siblings like 'connect' and 'openfinance_list_connections' by specifying its role as a pre-connect search.

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?

Explicitly says 'Call this BEFORE connecting' and explains that keywords are required, with a fallback hint. However, it does not explicitly list when not to use it, though the context implies it's for targeted search, not bulk listing.

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

All ASA 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
Disambiguation3/5

The openfinance_* family is mostly well-differentiated by resource type, but several tools overlap in purpose: openfinance_get_account_balance, openfinance_get_accounts_detail, and openfinance_list_accounts all return account/balance data, and openfinance_list_transactions versus openfinance_list_transactions_by_item have similar scopes. The marketplace tool also bundles many sub-actions (search, invoke, install, subscribe, report_bug, prompt library) into one tool, and duplicates the standalone report_bug tool. Detailed descriptions help, but an agent could easily misselect among the account and transaction variants.

Naming Consistency4/5

Naming is largely consistent: the finance tools follow a clear openfinance_verb_noun pattern (list_accounts, get_account_balance, force_sync, update_transaction_category). There are minor singular/plural inconsistencies (get_account_balance vs get_accounts_detail, get_credit_card_bill vs list_credit_card_bills) and generic platform verbs like authenticate/connect/marketplace that follow a different style, but the overall pattern is predictable and readable.

Tool Count3/5

25 tools is at the upper boundary of what feels manageable for a server covering platform management, marketplace operations, and a broad Open Finance data domain. The count is defensible given the many resource types (accounts, transactions, bills, loans, investments, connections), but it is heavy and the marketplace tool alone packs a dozen sub-capabilities into one entry, making the surface feel larger than 25 discrete tools.

Completeness5/5

The Open Finance surface is quite complete: connection lifecycle (list, connect, disconnect, force sync, status, provider status), account and balance reads, transactions with categorization support, credit card bills with payment status, loans, investments, and investment transactions. Platform concerns like authentication, versioning, toolkit state, marketplace search/install/invoke, and bug reporting are also covered, leaving no obvious dead ends for the server's stated purpose.

Resources