Skip to main content
Glama

Reembolsar pago

reembolsar_pago
Destructive

Issue full or partial refunds for charged customer payments; confirm the payment and amount before moving real money in live mode.

Instructions

Devuelve dinero de un pago cobrado al cliente, total o parcial. Mueve dinero real en modo live: confirma SIEMPRE con el usuario el pago y el monto antes de llamarla.

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": "reembolsar_pago"
  }
}

Input Schema

NameRequiredDescriptionDefault
montoNoMonto a reembolsar en pesos. Omítelo para reembolsar todo lo disponible.
motivoNo
pago_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so irreversibility is covered structurally; the description adds genuinely new context that this operates on live money and therefore needs user confirmation. It omits one behavior the annotations imply but do not explain: idempotentHint=false means a retried call could issue a second refund, a risk worth stating on a money-moving tool.

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?

Two sentences, purpose front-loaded, then the safety precondition in caps for emphasis. No filler, no restatement of the title, and the most important operational warning is the last thing read before acting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent money-movement tool with no output schema, the definition covers purpose and the confirmation gate but leaves meaningful gaps: it says nothing about what is returned (refund identifier/status), whether multiple partial refunds against the same pago_id are allowed, or failure conditions such as insufficient refundable balance. Adequate to avoid gross misuse, not complete.

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 coverage is only 33%: monto is documented in the schema (with the useful 'omit to refund everything available' rule), but motivo and pago_id have no descriptions at all. The description only echoes 'el pago y el monto' in the confirmation sentence and never explains what motivo is for or what pago_id must reference, so it does not compensate for the coverage gap.

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?

Names a concrete verb and resource ("Devuelve dinero de un pago cobrado al cliente") and states the scope variant (total o parcial). The verb alone cleanly separates it from every sibling (consultar_pago, listar_pagos, cancelar_link), which are read or link-management operations rather than money movement.

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

Usage Guidelines4/5

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

Gives a hard precondition for invocation: confirm the payment and amount with the user first, because it moves real money in live mode. That is stronger than most usage guidance. It stops short of 5 because it offers no when-not guidance or alternatives, e.g. how it relates to cancelar_link for an uncharged payment link.

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