Skip to main content
Glama

Neon 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.2/5.0
Behavior4/5

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

Annotations indicate read-only and idempotent. The description adds context: returns connector details, caveat warnings for non-Open-Finance connectors, and plan-based filtering. 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is quite detailed and somewhat lengthy, but each sentence adds value. It is front-loaded with the main purpose, but could be slightly more concise.

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?

Covers key behaviors: what is returned, caveat warning, plan handling, and when to call. No output schema, but the description provides sufficient information for an agent to invoke correctly.

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?

With 0% schema description coverage, the description compensates by explaining the purpose of 'keywords' (with examples) and 'include_accounts'. It also clarifies that 'keywords' is required in practice.

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 it searches bank connectors by name and returns specific fields including a connect_url. It distinguishes from sibling tools by advising to call this before connecting.

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 advises 'Call this BEFORE connecting' and explains that keywords are required (without it returns a hint). Mentions plan behavior, but does not explicitly contrast with all siblings.

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

All Neon 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.9/5.0
Disambiguation4/5

The openfinance_* family is cleanly separated by resource and action, and tricky pairs like list_accounts vs get_account_balance and list_transactions vs list_transactions_by_item are explicitly cross-referenced in descriptions. However, marketplace bundles a large set of sub-actions, and connect/toolkit_info partially overlap on reporting connection state, so a couple of boundaries are fuzzy.

Naming Consistency4/5

The openfinance_* tools consistently follow a verb_resource pattern with snake_case, which is highly predictable. The generic platform tools mostly fit the same style, but marketplace and toolkit_info are noun-only names, and openfinance_provider_status also breaks the verb pattern, so it is not perfectly uniform.

Tool Count3/5

At 25 tools, this server falls at the heavy end of the borderline range. The many openfinance_* list/get tools are individually justified for the financial domain, but adding platform tools like marketplace, connect, toolkit_info, and show_version makes the overall surface larger than a minimal server needs.

Completeness5/5

The financial surface is remarkably thorough: accounts, transactions, credit card bills, loans, investments, categories, connection lifecycle, sync, and provider health are all covered with list/get and update paths where applicable. The platform side also covers auth, connection status, marketplace discovery/execution, versioning, and bug reporting, leaving no obvious dead ends.

Resources