Skip to main content
Glama

Conta Bemol 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, idempotentHint, and destructiveHint. The description adds valuable behavioral context: that the reconnect_url does not consume a connection slot and does not require disconnecting first, which is not evident from annotations alone.

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 a single paragraph that efficiently conveys the main purpose, key fields, and important usage notes. It is front-loaded with the return value and includes necessary details without redundancy.

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 and zero parameters, the description provides sufficient context about the return values and their semantics. It explains both URLs adequately, making the tool's behavior complete for an API listing tool.

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 (coverage 100%). The description adds meaning by detailing the return fields and their significance (e.g., reconnect_url for UPDATE mode, add_connection_url for linking additional banks).

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 the tool returns saved bank connections with specific fields (connector_id, item_id, bank name, reconnect_url, add_connection_url). It distinguishes itself from sibling tools by explaining the reconnect_url's purpose in updating existing connections.

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 explicitly explains when to use the reconnect_url (e.g., for re-authentication, LOGIN_ERROR, stale data). It implies the tool is for listing connections, but does not explicitly state when not to use it, though the 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 Conta Bemol 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

Every tool has a clearly distinct purpose: accounts, transactions, credit card bills, loans, investments, connections, sync, categories, provider status, and platform meta-tools are all separable. Even the two transaction tools differ (per-account list vs consolidated analysis) and the two status tools differ (connection vs provider health).

Naming Consistency4/5

The openfinance_* prefix is consistently applied across the financial domain, and most follow a verb_noun pattern (list_accounts, get_balance, update_category). However, there are non-prefixed tools (authenticate, connect, marketplace, toolkit_info) and one outlier like openfinance_provider_status (noun instead of verb) that slightly break the pattern.

Tool Count3/5

25 tools is at the upper boundary of what feels heavy for a single server, even for a comprehensive financial aggregation toolkit. The number is justified by the breadth of domains covered (accounts, credit, loans, investments, connections, platform features), but it requires careful agent selection and might be better split into separate servers.

Completeness5/5

The surface covers the full financial data lifecycle: listing and fetching details for all asset types, updating transaction categories, managing connections (list, sync, disconnect, reauth), checking provider health, and searching connectors. There are no obvious dead ends—every domain has read and appropriate write/update operations.

Resources