Skip to main content
Glama

Consultar link de cobro

consultar_link
Read-only

Retrieves the status of a payment link—open, paid, expired, or canceled—using its link ID.

Instructions

Muestra el estado de un link de cobro (abierto, pagado, vencido o cancelado).

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

Input Schema

NameRequiredDescriptionDefault
link_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 bar is lower. The description adds that the result is a status drawn from four enumerated values (abierto, pagado, vencido, cancelado), which is genuinely useful return-value context, but says nothing about behavior for an invalid or unknown link_id, nor about any other returned fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the status enumeration is inserted where it is most useful. It is efficient; the only shortfall is that brevity here borders on under-specification rather than crisp completeness.

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?

With no output schema, the description carries some of the burden of explaining returns, which the status list partially does. However, for a lookup tool the agent still lacks the id format and what else the response contains (amount, buyer, expiration), so coverage is only adequate.

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?

There is one required parameter, link_id, and schema description coverage is 0%, so the schema gives no format or provenance details. The description only connects it implicitly ('link de cobro'); it does not say where the id comes from or what shape it takes. It neither compensates for nor worsens the coverage gap.

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?

Specific verb+resource ('Muestra el estado de un link de cobro') and it even enumerates the possible states, so the agent knows exactly what it retrieves. It does not distinguish itself from siblings like consultar_pago or listar_links, which is the only thing keeping it from a 5.

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 implicit: needing a link's status implies calling this with its id. There is no statement about when this is preferable to listar_links or consultar_pago, and no prerequisites or failure conditions are mentioned.

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