Skip to main content
Glama

Crear link de cobro

crear_link_de_cobro

Create a card payment link for a merchant and return its URL to send to a customer via WhatsApp or email; list merchants first if the merchant ID is unknown.

Instructions

Crea un link de cobro con tarjeta para un comercio y devuelve la URL para enviársela al cliente (por WhatsApp o correo). Si no sabes el comercio, usa primero listar_comercios.

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": {
      "comercio_id": "<comercio_id>",
      "monto": "<monto>",
      "concepto": "<concepto>"
    },
    "name": "crear_link_de_cobro"
  }
}

Input Schema

NameRequiredDescriptionDefault
itbisNoParte del monto que es ITBIS, en pesos. Omítelo si está exento.
montoYesTotal a cobrar en pesos, ITBIS incluido. Ej: "4,500.00".
idiomaNoIdioma de la página de pago. Por defecto es.
conceptoYesQué se cobra. Ej: "Cuota de mantenimiento octubre, Apto 4B".
referenciaNoTu referencia interna (factura, cuota). Vuelve en los webhooks.
comercio_idYesId del comercio (mer_…).
vence_en_diasNoDías hasta que vence el link. Por defecto 30.
cliente_correoNo
cliente_nombreNo
cliente_telefonoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the response is a shareable URL, but it never warns that repeated calls create duplicate links (non-idempotent) or that the link expires, which matters for a creation 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 front-loaded sentences with zero filler: the action and return value come first, the routing hint second. Nothing could be removed without losing information.

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 10-parameter creation tool with no output schema, the description covers the action, the returned URL, currency context via the schema, and the merchant prerequisite. It is missing only expiration and duplicate-creation behavior, which are secondary but non-trivial for a payment link.

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?

With 70% schema coverage and 10 parameters, the schema already documents monto, concepto, referencia, vence_en_dias and idioma with examples. The description only implicitly ties comercio_id to listar_comercios and adds no format or constraint detail beyond the schema, so baseline 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?

States a concrete verb+resource ("Crea un link de cobro con tarjeta") and adds the outcome ("devuelve la URL para enviársela al cliente"), which tells an agent this is the creation path distinct from consultar_link or listar_links. It stops short of explicitly contrasting with those siblings.

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 an explicit prerequisite and fallback: "Si no sabes el comercio, usa primero listar_comercios." That is real routing guidance, though it says nothing about when to prefer consultar_link/cancelar_link or about preconditions like an active merchant account.

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