Skip to main content
Glama

Mercado Pago MCP

by io.github.mcp-dir

openfinance_provider_status

Read-onlyIdempotent

Checks the LIVE operational status of the Open Finance provider (its public status page) — this is the PROVIDER's health, separate from your own connection's openfinance_get_item_status. Use it whenever data looks incomplete or stale even though a connection shows UPDATED (accounts/transactions/balances missing, a bank not returning everything): it reveals an upstream outage or a known incident on a specific bank/connector, so you can tell a provider-side problem apart from a connection that just needs reconnecting. Returns the global indicator (none/minor/major/critical), degraded components, open incidents, and — when you have banks connected — flags the incidents that affect YOUR connected banks in your_banks_affected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds context: it checks a public status page, is independent of user connections, and details the output (global indicator, components, incidents, your_banks_affected). No contradiction.

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 dense paragraph but effectively front-loads the main action and provides all necessary details. It could be slightly more structured, but it is concise relative to the information conveyed.

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 parameters and no output schema, the description fully covers the tool's purpose, usage triggers, and output types (global indicator, degraded components, incidents, your_banks_affected). 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?

The input schema has no parameters (0 params, 100% coverage), so the description does not need to add parameter info. Baseline for 0 params is 4, and no additional parameter semantics are required or missing.

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 'checks the LIVE operational status of the Open Finance provider', distinguishing it from the user's own connection status via sibling tool 'openfinance_get_item_status'. Verb and resource are specific and unambiguous.

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?

Explicitly tells when to use: 'whenever data looks incomplete or stale even though a connection shows UPDATED' and how it helps differentiate provider-side problems from connection issues. Includes what is returned, providing clear context for selection.

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