Skip to main content
Glama

Guía de uso

wetaca_usage
Read-onlyIdempotent

Read the canonical usage guide before changing a Wetaca menu, subscription, order, coupon, or address; it explains confirmation rules, exit codes, and typical flows for safe account changes.

Instructions

Guía canónica para agentes, la misma que wetaca skills get wetaca-usage. Léela antes de cambiar el menú, la suscripción, un pedido, un cupón o una dirección. Incluye códigos de salida, reglas de confirmación y flujos típicos. Solo lectura y sin red.

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

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

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the tool is read-only, needs no network, and returns exit codes, confirmation rules and typical flows — genuinely useful behavioral context for a documentation tool. One tension: "sin red" sits awkwardly beside openWorldHint=true, though this reads as a reassurance about side effects rather than a flat contradiction.

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?

Three short sentences, front-loaded with the identity of the tool and followed by the read-before-mutate instruction and a content summary; no filler. The CLI-equivalence clause is slightly technical but earns its place by pinning down the canonical source.

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 zero-required-parameter documentation tool with no output schema, the description covers what the guide contains and when to consult it. It does not state the return form (e.g., markdown text blob) or its size, which is the main remaining gap for an agent deciding whether to load it.

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%, so both optional parameters (debug, profile) are already explained in the input schema, including the default-profile fallback. The description adds nothing about them, which is acceptable at full coverage but leaves it at the baseline.

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

Purpose5/5

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

"Guía canónica para agentes" names a specific resource (the usage guide) and equates it with the CLI command `wetaca skills get wetaca-usage`, so an agent knows exactly what it retrieves. The sentence listing what it covers (códigos de salida, reglas de confirmación, flujos típicos) makes it unmistakable against the sibling mutation tools such as wetaca_orders_cancel or wetaca_config_set.

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

Usage Guidelines4/5

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

"Léela antes de cambiar el menú, la suscripción, un pedido, un cupón o una dirección" gives an explicit trigger tied to the families of sibling write tools, which is strong routing. It stops short of a when-not statement (e.g., that it is unnecessary for pure reads) or naming another tool, so it is clear but not fully discriminating.

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