Skip to main content
Glama

Sicoob 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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds meaningful behavioral context beyond annotations (e.g., reconnect_url behavior, update mode, no slot consumption) without contradicting 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?

Two sentences, front-loaded with the core purpose and output fields. No wasted words; every sentence serves a purpose.

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?

For a simple list tool with no parameters and no output schema, the description is complete. It covers purpose, output fields, and special behavior of the reconnect URL. No gaps.

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?

Input schema has no parameters, so the baseline is 4. The description adds value by explaining the output fields and special URLs (reconnect_url, add_connection_url), which is more than just schema coverage; it helps the agent understand the return data.

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 'Returns the saved bank connections' with specific output fields (connector_id, item_id, bank name, reconnect_url, add_connection_url). This is a specific verb+resource, and it distinguishes itself from sibling tools like openfinance_list_accounts or openfinance_get_item_status by focusing on 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?

It provides explicit guidance on when to use the reconnect_url ('when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data)') and states it does not consume a slot or require disconnecting first. While it doesn't contrast with all siblings, the context is clear enough for an AI agent.

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

All Sicoob 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.7/5.0
Disambiguation4/5

Most openfinance_* tools target clearly distinct resources (accounts, transactions, bills, loans, investments, connections, categories). Minor overlap exists—list_accounts returns balances and list_transactions_by_item consolidates what list_transactions provides—but the detailed descriptions distinguish them adequately.

Naming Consistency4/5

The openfinance_* tools follow a consistent verb_noun pattern (get_*, list_*, update_*, force_sync, search_*) with one slight deviation: openfinance_provider_status omits a verb. The non-openfinance platform tools (authenticate, connect, marketplace, report_bug, etc.) break the prefix pattern, creating two naming conventions within the same server.

Tool Count3/5

25 tools sits at the upper boundary of acceptable for a comprehensive Open Finance banking adapter, covering accounts, transactions, credit cards, loans, investments, and connection management. However, including meta-platform tools like marketplace and toolkit_info inflates the count and makes the set feel heavier than a pure banking tool surface.

Completeness4/5

The tool surface covers the core Open Finance lifecycle well: list/get accounts, balances, transactions, credit card bills, loans, investments, connection management, category correction, and provider status. Gaps include no direct new-bank connection tool (only URLs) and no investment detail endpoint beyond transactions, but agents can work around these.

Resources