Skip to main content
Glama

Mercado Pago MCP

by io.github.mcp-dir

openfinance_force_sync

Forces the bank to re-sync one or more connections NOW and WAITS for it to finish (PATCH /items/:id, then polls until the item stops updating, up to ~60s). Use this when a balance or transaction list looks stale: a connection can read UPDATED yet be hours old, and this pulls fresh data WITHOUT disconnecting/reconnecting. Pass items as an array of selectors (item_id, connector_id, connector_name, or the user-set custom_label nickname); OMIT items to sync ALL linked banks. Returns { results, errors }; each result has the final status, executionStatus, lastUpdatedAt (advances when data is refreshed), and synced (true = fresh data is ready). needs_action (e.g. MFA_REINTERACTION / LOGIN_ERROR / WAITING_USER_INPUT) means the user must re-authenticate — those results include a reconnect_url that opens the widget in UPDATE mode for that exact connection (user enters credentials / MFA token, data refreshes in place, no slot consumed, no disconnect needed). timed_out: true means the sync is still running — re-check with openfinance_get_item_status. Set wait: false for fire-and-forget (returns immediately while UPDATING).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNo
itemsNo

TDQS

A4.9/5.0
Behavior5/5

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

The description fully discloses the behavioral traits: it waits up to ~60s, polls for completion, and provides timed_out flag. It explains what happens on needs_action (reconnect_url for re-authentication). Annotations are minimal (only readOnlyHint=false), so the description carries the full burden and meets it comprehensively.

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 thorough but not overly verbose. It is well-structured: main action, usage, parameters, return fields, edge cases. It could be slightly more concise, but every sentence adds 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 no output schema, the description explains the full return format including status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url, and timed_out. It covers the polling behavior and error cases. This is complete for a tool with 2 parameters and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates fully. It explains `items` as an array of selectors (item_id, connector_id, etc.) and that omitting it syncs all. For `wait`, it explains that setting it to false gives fire-and-forget behavior. This adds essential meaning beyond the 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 that the tool forces a bank to re-sync connections and waits for completion. It explicitly differentiates from sibling tools like openfinance_get_item_status by explaining when to use each. The verb 'forces' and resource 'connections' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance ('Use this when a balance or transaction list looks stale') and when-not-to-use (e.g., re-check with openfinance_get_item_status if timed_out). It explains the implications of omitting `items` (sync all) and setting `wait: false` (fire-and-forget).

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