Skip to main content
Glama

Get payment

get_payment
Read-only

Retrieve a Mercado Pago payment by ID to inspect its status, amounts, payer, fees, and refunds.

Instructions

Fetch one Mercado Pago payment by ID, including status, status_detail, amounts, payer, fees, and refunds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payment_id": "<payment_id>"
    },
    "name": "get_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_idYesPayment ID (numeric, as string or number)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-API profile is covered by structured data. The description adds the useful fact that the response includes status_detail, fees, and refunds, which goes beyond the annotations, but it says nothing about error behavior for unknown IDs, rate limits, or authentication requirements.

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?

A single front-loaded sentence with the verb and resource first and the returned fields trailing as supporting detail. There is no redundant restatement of the title and no filler.

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?

For a one-parameter read tool whose annotations already cover safety, this is close to complete: the field enumeration partially substitutes for the absent output schema. Minor gaps remain around unknown-ID behavior and authentication, but nothing needed to invoke the tool correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100% and the single required payment_id parameter is fully documented in the schema, including its accepted string-or-integer forms and numeric pattern. The description only restates "by ID" and adds no format or edge-case guidance beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Fetch one Mercado Pago payment by ID" gives a specific verb (fetch), a specific resource (payment), and a scope qualifier (one, by ID) that implicitly separates it from search_payments. It also enumerates the payload contents. No sibling is named explicitly, so differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

Usage is implied: call this when you already have a payment ID and want the full record for that single payment. There is no explicit when-to-use / when-not-to-use guidance, no mention of when to prefer search_payments or get_merchant_order, and no note about prerequisites such as valid credentials or IDs from a different environment.

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