Skip to main content
Glama

Méliuz 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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

While readOnlyHint and idempotentHint are already declared, the description adds plan-dependent filtering, caveat disclosure, and the behavior when keywords are omitted (returns hint instead of dumping catalog).

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?

Description is detailed but front-loaded with core function and then covers nuances. Each sentence adds value, though length could be slightly reduced without losing clarity.

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, description fully explains return fields, plan behavior, and caveats. Provides everything an agent needs to use the tool 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?

Schema coverage is 0%, so description compensates by explaining keywords with examples and required status, and include_accounts triggers returning linked connections. Adds meaning beyond bare schema types.

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, returning specific fields like connector id, access type, audience, and connect_url. It distinguishes itself from sibling tools by being the search/selection step 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 Guidelines5/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 required keywords, when to surface caveat, and how plan affects results. Provides clear context for when and how to use.

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

All Méliuz 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.2/5.0
Disambiguation5/5

Each tool targets a distinct operation or data type (accounts, transactions, bills, loans, investments, connections, etc.) with no ambiguity. Even closely related tools like openfinance_list_transactions and openfinance_list_transactions_by_item are clearly differentiated by scope and output format.

Naming Consistency3/5

The majority of tools follow the 'openfinance_' prefix for banking operations, but utility tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break this pattern, creating an inconsistent mix. However, the convention is still readable and the utilities are clearly distinct.

Tool Count4/5

25 tools is on the high side but well-justified by the breadth of Open Finance data types (accounts, transactions, credit cards, bills, loans, investments) and supporting operations (sync, status, search, updates). A few tools could potentially be merged, but overall the number is reasonable for the domain.

Completeness4/5

The tool surface covers the core Open Finance workflows: listing, reading details, syncing, updating categories, and checking provider status. Minor gaps exist (e.g., no tool to create or delete accounts/transactions), but these are external constraints. The set enables most user-facing financial queries and actions.

Resources