Skip to main content
Glama

Límites de tarjeta regalo

wetaca_giftcards_show
Read-onlyIdempotent

Retrieves the minimum and maximum amounts for Wetaca gift cards. Use it to check gift card value limits without viewing or charging payment cards.

Instructions

Equivale a wetaca giftcards show. Importes mínimo y máximo de las tarjetas regalo. Solo lectura. No muestra ni cobra tarjetas de pago.

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

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Solo lectura' merely repeats structured data. What does add value is the negative scoping ('No muestra ni cobra tarjetas de pago'), which tells the agent the call will not return a card list and will not mutate anything, but no auth requirements, rate limits or output format are mentioned.

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?

Four short sentences with the resource and return values front-loaded after a fairly low-value CLI equivalence line. Nothing is padded, but the 'Equivale a `wetaca giftcards show`' sentence mostly duplicates the name and could be dropped for an agent-facing reader.

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

Completeness4/5

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

For a simple, parameter-light, read-only tool with no output schema, the description names what comes back (min and max amounts) and what does not (card data, charges), which is enough to call it confidently. A brief note on the response shape (single pair vs per-card values) would close the 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?

The two parameters (debug, profile) are fully described in the schema, and the description says nothing about them, which is acceptable at 100% schema coverage. The CLI-mapping sentence does not add meaning to any parameter, so the baseline of 3 applies.

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?

The description states the resource (tarjetas regalo) and what is returned (importes mínimo y máximo), which is more specific than the title. It also rules out two adjacent behaviors ('No muestra ni cobra tarjetas de pago'), separating it from a redemption or listing tool, though it never names the redeem sibling outright.

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 implied: read 'Solo lectura' and 'no cobra' and the agent infers this is the tool for reading gift-card limits rather than redeeming. There is no explicit when-to-use statement or named alternative pointing at wetaca_giftcards_redeem when the user actually wants to redeem.

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