Skip to main content
Glama

Listar links de cobro

listar_links
Read-only

List recent payment links, filtered by status or reference, to review collections and track payment-link activity.

Instructions

Lista links de cobro recientes. Puede filtrar por estado o por referencia.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listar_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
estadoNoopen = pendiente de pago.
cantidadNo
referenciaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this as a safe read, so the description only needs supplemental context. It adds the "recientes" scoping hint, but does not say what the default result size or ordering is, whether results are capped, or how the 50-item maximum behaves — meaningful gaps for a list operation.

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?

Two tight sentences with no filler, and the core purpose is front-loaded. The brevity is efficient, though it borders on under-specification rather than tightness.

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

Completeness2/5

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

For a three-parameter list tool with no output schema, the description omits default result count, sort order, pagination behavior, and the meaning of referencia matching. An agent could call it, but not predict what it will get back or how to narrow results reliably.

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?

With only 33% schema description coverage, the description must compensate and it largely does not. It names the estado and referencia filters but adds no semantics — no matching rules for referencia (exact vs partial), no default behavior when omitted, and it never mentions the cantidad limit parameter at all.

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?

"Lista links de cobro recientes" gives a specific verb plus resource and adds a recency qualifier, so the agent knows this is a read of a collection. It does not distinguish itself from siblings such as consultar_link (single link) or listar_pagos, so differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says when to prefer this over consultar_link for a specific link, nor how it relates to listar_pagos. The sentence about filtering describes parameters rather than selection criteria, leaving usage entirely implied.

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