Skip to main content
Glama

Cupón de la semana

wetaca_vouchers_current
Read-onlyIdempotent

Retrieve the voucher applied to the next Wetaca week, if one exists, to check current discounts without making changes.

Instructions

Equivale a wetaca vouchers current. Cupón aplicado a la próxima semana, si hay alguno. 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_current"
  }
}

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.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and "Solo lectura" simply repeats that rather than adding context. The one piece of new behavior is that no voucher may exist for the next week, so a null/empty outcome is possible — useful but minimal. No return shape, error behavior, or auth requirement is described.

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?

It is short and front-loaded with the substantive clause about the coupon, which is good. However, the first sentence is pure redundancy with the tool name and consumes roughly a third of the text without adding information.

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 read-only lookup with rich annotations and fully documented parameters, the minimum is met. Since there is no output schema, the description could still have said what a voucher looks like (code, discount, validity) or what happens when none exists, which is a real gap for an agent consuming the result.

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 fully documented in the schema, so the baseline applies. The description says nothing about parameters beyond what the schema already carries, but it does not need to.

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?

"Cupón aplicado a la próxima semana, si hay alguno" does identify a specific resource and time scope, but the opening sentence ("Equivale a `wetaca vouchers current`") merely restates the tool name in prose and adds nothing. It also does not distinguish this from vouchers_list or vouchers_apply, which the agent could easily confuse with 'current'.

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 explicit when-to-use guidance and no mention of alternatives such as wetaca_vouchers_list (all vouchers) or wetaca_vouchers_apply. The qualifier "si hay alguno" hints that the result may be empty, but the agent is left to infer when to call this versus a sibling.

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