Skip to main content
Glama

Mercado Pago 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.4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint: true and destructiveHint: false, which the description reinforces by stating it returns data. The description adds context about reconnect_url behavior (UPDATE mode, no slot consumption). No contradiction with annotations.

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 of three sentences, front-loaded with the main purpose. While it could be slightly more concise by omitting obvious field names, it is not overly verbose and every sentence contributes value.

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?

Given the tool is a simple list with no parameters, the description completely covers its functionality. It explains all key return values and the special URLs, leaving no ambiguity for an AI agent.

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?

No input parameters, so schema coverage is 100%. The description adds meaning by explaining the return fields (connector_id, item_id, bank name, reconnect_url, add_connection_url) and their behavioral significance, 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 the tool returns saved bank connections with specific fields (connector_id, item_id, bank name, reconnect_url, add_connection_url). It distinguishes from sibling tools like openfinance_disconnect_bank and openfinance_force_sync by focusing on listing and providing URLs for reconnection.

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 explicit guidance on when to use the reconnect_url (for re-authentication, LOGIN_ERROR, stale data) and what it does (opens widget in UPDATE mode). It also notes that reconnect does not consume a connection slot. However, it does not explicitly state when not to use this tool versus alternatives like openfinance_disconnect_bank.

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

All Mercado Pago 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
Disambiguation5/5

Each tool has a clearly distinct purpose. Even overlapping-looking tools like list_transactions vs list_transactions_by_item are clearly differentiated (per-account vs consolidated per-connection), and get vs list variants follow standard conventions. The marketplace tool bundles multiple actions but is its own meta-tool. No two tools appear to do the same thing.

Naming Consistency4/5

The openfinance_ prefix provides a consistent pattern for banking operations, with clear get/list/update/force_sync verbs. A few non-prefixed meta tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break the pattern, but they represent different functional domains and are still readable. Overall the convention is predictable.

Tool Count3/5

At 25 tools, this is on the heavy side per the calibration guidelines (16-25 feels heavy). However, the breadth of Open Finance resources (accounts, transactions, investments, loans, credit cards, connections, plus meta operations) largely justifies the count. It's borderline and could benefit from consolidation, but it's not excessive.

Completeness4/5

The tool surface covers the domain comprehensively: listing and getting accounts, transactions, investments, loans, credit card bills, connections, status, sync, category management, and provider health. Missing operations are minor (e.g., no explicit 'get single transaction' but list covers it; no create/update on banking data besides category and disconnect). Core workflows are fully supported.

Resources