Skip to main content
Glama

Listar pagos

listar_pagos
Read-only

Lists recent payments with an optional status filter, so you can review collection activity and confirm transaction outcomes.

Instructions

Lista pagos recientes, con filtro opcional por estado.

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_pagos"
  }
}

Input Schema

NameRequiredDescriptionDefault
estadoNosucceeded = cobrado.
cantidadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read. The description adds the useful facts that results are "recientes" and filtering is optional, but leaves undefined what "recent" means (no date window), what the default page size is, and how results are ordered — all relevant for a listing tool.

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 wasted wording. It is efficient, though the terseness leaves the missing default-count information unaddressed.

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 simple two-parameter read-only list tool with no output schema, the description covers the essentials but not the operational details an agent needs: what counts as "recent", the default/returned quantity, and result ordering.

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 50%: estado carries its own description ("succeeded = cobrado") while cantidad has no description or default. The description explains only the estado filter and omits cantidad entirely, so it fails to compensate for the undocumented parameter.

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 and resource ("Lista pagos") and adds scope: recent payments with an optional status filter. It does not differentiate from the sibling consultar_pago, which handles single-payment lookup, so an agent must infer the boundary.

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?

The optional status filter hints at when to use it (browsing payments by state), but there is no explicit guidance on when to prefer consultar_pago or resumen_de_cobros instead, nor any prerequisite or paging guidance.

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