Skip to main content
Glama

Uber Conta by 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.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/destructive hints, but the description adds substantial behavioral detail: the reconnect_url opens a widget in UPDATE mode, requires re-entering credentials/MFA, and refreshes in place. It also clarifies the add_connection_url purpose and the no-slot/no-disconnect behavior.

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?

Two sentences, front-loaded with the main purpose, and every clause adds value—listing fields, explaining URL semantics, and stating constraints. No filler.

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?

For a zero-parameter tool with no output schema, the description covers the main return fields and semantics of both URLs. It could add example output structure or error states, but it's largely complete.

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 tool has zero parameters (input schema is empty), and the baseline for 0 params is 4. The description doesn't need to explain parameters; it focuses on return values, which is appropriate.

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 states 'Returns the saved bank connections for this install' with a specific verb and resource. It lists the returned fields including unique URLs, distinguishing it from sibling list tools like openfinance_list_accounts or openfinance_list_transactions.

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 explains the reconnect_url's use case ('use it when a connection needs re-authentication') and clarifies that it doesn't consume a slot or require disconnecting. While it doesn't name alternative tools, it provides clear context for when this tool's outputs are needed.

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

All Uber Conta by 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.3/5.0
Disambiguation4/5

The openfinance_* tools are mostly distinct list/get/update/sync operations, and the non-openfinance tools are clearly separate platform utilities. A few pairs could be confused, such as openfinance_list_accounts vs openfinance_get_accounts_detail, or openfinance_get_item_status vs openfinance_list_connections, but the descriptions generally make the intended use clear.

Naming Consistency4/5

The domain tools follow a consistent openfinance_verb_noun pattern, making the bulk of the API predictable. The deviation comes from the six non-prefixed platform tools, and one or two names like openfinance_provider_status are noun-led rather than verb-led, but overall the convention is coherent.

Tool Count3/5

25 tools is at the heavy end of the range, and the server would feel tighter if some get/list pairs were consolidated. However, the breadth is somewhat justified by the number of Open Finance resource types covered: accounts, transactions, bills, investments, loans, connections, categories, and sync/status operations plus platform utilities.

Completeness5/5

The Open Finance surface is thorough: connection lifecycle, account data, balances, transactions, credit card bills, investments, loans, categories, sync, and provider health are all covered. There are no significant dead ends, and the additional platform tools handle authentication, marketplace discovery, and system information.

Resources