Skip to main content
Glama

Consultar pago

consultar_pago
Read-only

Retrieve a payment’s status, amount, card details, and refunds by payment ID to verify transactions and resolve payment inquiries.

Instructions

Muestra el detalle de un pago: estado, monto, tarjeta y reembolsos.

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": {
      "pago_id": "<pago_id>"
    },
    "name": "consultar_pago"
  }
}

Input Schema

NameRequiredDescriptionDefault
pago_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's extra value is the return payload — status, amount, card and refunds — which is genuinely useful context. It omits error behavior for a bad pago_id, currency/formatting assumptions, and any auth or rate-limit notes.

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 short sentence, front-loaded with the verb and the resource, with no filler or redundancy. Every clause lists information the caller gains from the call.

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 with no output schema, naming the returned fields is the key missing piece and it is present. The remaining gaps (pago_id format, not-found behavior) are minor but real given 0% schema coverage.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description carries the burden — yet it says nothing about pago_id's format, prefix, or where the agent would obtain one. The phrase "un pago" only weakly implies that the ID identifies the resource.

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?

Concrete verb+resource ("Muestra el detalle de un pago") plus an enumeration of the fields returned (estado, monto, tarjeta, reembolsos), which lets an agent tell it apart from listar_pagos/reembolsar_pago in spirit. It stops short of naming a sibling or delimiting scope explicitly, so it's clear but not fully differentiated.

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 only implied: asking for the "detalle de un pago" signals a single-payment lookup by ID. There is no explicit when-to-use, no note on when to prefer listar_pagos for browsing, and no mention of what to do if the payment does not exist.

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