Skip to main content
Glama

Banco Digio 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

TDQS

A4.6/5.0
Behavior5/5

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

Adds significant behavioral context beyond annotations: batch response shape `{ results, errors }`, provider_incident block with reliability warnings. Annotations already indicate readOnly, destructive=false, idempotent, and description aligns with them.

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?

Efficiently structured: purpose first, then parameter details, then warning. No redundant information.

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 the primary use case, parameter constraints, and unexpected behavior (provider_incident). Could benefit from mentioning what fields are in the full account objects beyond creditData.

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?

Only parameter account_ids is described with range (1-50) and batch shape, adding meaning beyond the schema which only defines type array of strings.

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?

Description clearly states 'Returns full account objects including extended creditData', specifies the endpoint pattern, and distinguishes from sibling tools like openfinance_list_accounts which likely return summaries.

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?

Describes when to use (to get full details with creditData), parameter constraints (array of 1-50 ids), and warns about provider_incident conditions. Lacks explicit when-not-to-use or alternatives.

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

All Banco Digio 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.1/5.0
Disambiguation4/5

Most tools map clearly to a distinct openfinance resource or action (accounts, transactions, bills, investments, loans, connections, provider health), and the platform utilities are a separate family. The only realistically confusable pairs are openfinance_list_transactions vs openfinance_list_transactions_by_item and openfinance_list_accounts vs openfinance_get_accounts_detail, but the descriptions draw sharp boundaries between them.

Naming Consistency4/5

The 19 openfinance_* tools follow a strong openfinance_<verb>_<noun> convention, with only minor exceptions like openfinance_provider_status and openfinance_list_transactions_by_item. The six platform tools mix bare verbs (authenticate, connect), nouns (marketplace, toolkit_info), and verb_noun (report_bug, show_version), but they are clearly a separate utility layer.

Tool Count3/5

25 tools sits at the top of the 'feels heavy' band. The number is defensible for a full Open Finance data product plus platform management tools, but an agent is exposed to a lot of surface area, and the same server mixes a banking-data adapter with a marketplace/utility layer.

Completeness5/5

The openfinance surface covers the full lifecycle: search/connect/reconnect/disconnect banks, force-sync, item status, provider incidents, accounts, balances, transactions per account and per connection, credit-card bills with paid-status derivation, investments and investment transactions, loans, loan detail, and transaction categorization. Platform tools cover auth, connection status, toolkit state, version, bug reporting, and marketplace operations, so there are no obvious dead ends.

Resources