Skip to main content
Glama

Listar cupones

wetaca_vouchers_list
Read-onlyIdempotent

List the vouchers on a Wetaca account in read-only mode, optionally using a named session profile, to review available coupons.

Instructions

Equivale a wetaca vouchers list. Cupones de la cuenta. Solo lectura.

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

Input Schema

NameRequiredDescriptionDefault
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
profileNoPerfil de sesión de wetaca-cli (--profile). Si se omite, usa el perfil por defecto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so "Solo lectura" merely restates structured data. The description adds nothing beyond that — no return shape, no pagination, no note on what an empty voucher list means.

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

Conciseness3/5

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

Three short fragments with no padding, so length is fine. The lead sentence is the CLI-equivalence mapping rather than the actual purpose, which is a weak front-load for an agent that does not know the CLI.

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 zero-required-parameter read-only list with rich annotations and no output schema, the definition is minimally sufficient to invoke correctly. It is incomplete on what the list returns and on how it relates to the other voucher tools, which is the main remaining gap.

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?

Schema description coverage is 100% and both parameters (debug, profile) are documented in the schema, so the description is not required to carry parameter meaning. It mentions neither parameter, which is acceptable at full coverage but adds no value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Cupones de la cuenta" plus the CLI equivalence establishes the resource (account vouchers) and, via the name/title, the list operation. However, it never distinguishes this from siblings like wetaca_vouchers_current or wetaca_vouchers_apply, so an agent must infer which voucher tool to pick from the name alone.

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 or when-not-to-use guidance, and no alternative is named. The only contextual signal is "de la cuenta", which does not tell an agent whether to call this versus listing current vouchers or applying one.

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