Skip to main content
Glama

Banco Digio MCP

by io.github.mcp-dir

openfinance_list_connections

Read-onlyIdempotent

Returns the saved bank connections for this install: connector_id, item_id, bank name, a per-connection reconnect_url, and an add_connection_url to link additional banks via the Open Finance widget. The reconnect_url reopens the widget in UPDATE mode for that EXISTING connection (user re-enters credentials / MFA token and the data refreshes in place) — use it when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data). It does NOT consume a connection slot and does NOT require disconnecting first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context about the reconnect_url behavior and that it does not consume connection slots. This adds value beyond annotations, though no inherent contradictions.

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 three sentences, efficiently packed with relevant information. It front-loads the primary purpose and includes details on the special URLs. Slightly verbose in the reconnect_url explanation but overall 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?

Given no output schema, the description adequately covers the return structure and key nuances (reconnect_url behavior). It lacks pagination or ordering details, but for a listing tool with readOnlyHint, this is acceptable completeness.

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?

The input schema has no parameters, so schema coverage is 100%. The description does not need to explain parameters but instead adds value by describing the output fields in detail, compensating for the lack of an output schema.

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 returns saved bank connections with specific fields (connector_id, item_id, bank name, reconnect_url, add_connection_url). The verb 'Returns' and the resource 'saved bank connections' are well-defined. It distinguishes from sibling tools by detailing the unique output and URLs.

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?

The description provides context on using the reconnect_url for re-authentication scenarios (MFA connectors, LOGIN_ERROR, stale data). It clarifies what the tool does NOT do (consume a connection slot or require disconnecting). However, it does not explicitly state when to use this tool over siblings like 'openfinance_get_item_status'.

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