Skip to main content
Glama

Banco Master MCP

by io.github.mcp-dir

openfinance_get_accounts_detail

Read-onlyIdempotent

Returns full account objects including extended creditData (additional cards, limits) per id (GET /accounts/:id). Pass account_ids as an array (1–50). { results, errors } batch shape. May include a provider_incident block when the Open Finance provider has an OPEN incident affecting a connected bank: credit limits and balances may be unreliable (e.g. a limit near 1,00) until the provider recovers. Do not present those values as real.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idsYes

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
Behavior5/5

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

Adds important behavioral details beyond annotations: batch {results, errors} shape, provider_incident block, and caution about unreliable values. 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?

Single paragraph with necessary info, front-loaded with purpose. Could be more structured but not verbose.

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?

Covers return shape, error handling, and special case of provider incidents. Without output schema, description provides sufficient context for correct use.

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%, but description compensates by stating parameter should be an array (1-50) of strings, implying account IDs. Adds constraint and type info.

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?

States it returns full account objects including extended creditData per ID, specifies HTTP method and endpoint pattern, and mentions batch shape. Clearly distinguishes from list tools like openfinance_list_accounts.

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?

Provides specific usage instructions: pass account_ids array (1-50) and explains batch shape. Does not explicitly mention when to avoid or prefer siblings, but context is clear.

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

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

Most openfinance_* tools are clearly separated by resource and action, and the long descriptions help, but several pairs can trip up an agent: authenticate/connect both deal with login/connection state, openfinance_list_transactions and openfinance_list_transactions_by_item sound nearly identical, and marketplace internally exposes report_bug/list_tools functions that also exist as top-level tools. This is more than a single ambiguous edge.

Naming Consistency3/5

The 19 openfinance_* tools follow a clean get_/list_/update_ pattern and are easy to navigate, but the platform-level tools break the convention: authenticate, connect, marketplace, toolkit_info, report_bug, and show_version mix bare verbs, nouns, and noun-noun compounds. The pattern is not chaotic, but it is definitely mixed.

Tool Count3/5

25 tools is on the heavy end of the borderline range and is a large working set for an agent. The openfinance tools are individually justified and support batching, but the extra platform/marketplace tools add scope and some redundancy with report_bug and toolkit_info.

Completeness5/5

For a bank-data aggregation server, the surface is complete: connector discovery, linking/reconnecting/disconnecting, account lists and details, balances, transactions, categorization, credit-card bills, investments, loans, sync status, and provider health are all covered. There are no obvious dead ends in the main workflows.

Resources