Skip to main content
Glama

Get preference

get_preference
Read-only

Fetch a Mercado Pago Checkout Pro preference by ID to inspect items, back URLs, notification URL, external reference, expiration, and init_point for payment flow review.

Instructions

Fetch a Checkout Pro preference by ID: items, back_urls, notification_url, external_reference, expiration, and init_point.

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": {
      "preference_id": "<preference_id>"
    },
    "name": "get_preference"
  }
}

Input Schema

NameRequiredDescriptionDefault
preference_idYesCheckout Pro preference ID, e.g. 123456789-0a1b2c3d-...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 profile is covered. The description adds value by listing the payload fields the caller will receive, which helps decide whether this call answers the question, but it says nothing about auth requirements, rate limits, or behavior when the ID does not exist.

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?

One sentence, front-loaded with the verb and resource, with the field enumeration packed into a compact list. Nothing is redundant or padded.

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 single-parameter read tool with no output schema, the field list effectively substitutes for a return-value spec, which is the key gap it needed to fill. It stops short of mentioning error cases or authentication, but nothing essential to invoking the call 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 preference_id parameter already carries a format pattern and example, so the description cannot add much. Its only contribution is the implicit confirmation that the ID identifies a Checkout Pro preference, which the schema already states.

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?

The description names a specific verb ("Fetch") and a specific resource ("a Checkout Pro preference") scoped by ID, and it enumerates the returned fields, so an agent knows exactly what it retrieves. It doesn't explicitly contrast itself with siblings like get_payment or get_merchant_order, but the resource noun is distinctive enough to separate them.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this tool versus get_payment or get_merchant_order, and no prerequisites such as needing valid API credentials or an existing preference ID. Usage is only implied by the phrase "by ID", leaving the agent to infer the selection rule.

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