Skip to main content
Glama

Cancelar link de cobro

cancelar_link
DestructiveIdempotent

Cancels an unpaid payment link so it can no longer be paid. Confirm with the user before use.

Instructions

Cancela un link que aún no se ha pagado, para que ya no se pueda pagar. Confirma con el usuario antes de usarla.

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": {
      "link_id": "<link_id>"
    },
    "name": "cancelar_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
link_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds real value by stating the effective consequence (the link becomes unpayable) and the precondition that gates it. It does not say what happens if the precondition is violated (error vs silent no-op), which is the main remaining behavioral gap.

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 tight sentences with no filler: the effect and its precondition come first, the confirmation guard second. Every clause carries information an agent needs.

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?

A one-parameter destructive tool with annotations covering safety and idempotency needs little description, and the core semantics are present. Still missing are the failure mode for an already-paid link and any note on the response, which matters for a destructive operation.

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% and the single parameter link_id is undocumented in both schema and description. The description never mentions the parameter, so an agent gets no guidance on whether link_id is an internal ID, slug, or URL — the tool cannot compensate here.

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?

Names a specific verb+resource pair ("Cancela un link") and adds the state precondition ("que aún no se ha pagado"), which separates it from paid-link flows like reembolsar_pago. It stops short of naming any sibling tool explicitly, so differentiation is inferred 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 Guidelines4/5

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

Gives clear usage context: only for links that are not yet paid, plus an explicit procedural requirement to confirm with the user first. It does not say what to do instead when the link is already paid (e.g. refund path), so the when-not branch is only implied.

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