Skip to main content
Glama

Ver suscripción

wetaca_subscription_show
Read-onlyIdempotent

Retrieve a Wetaca subscription's complete details, including profiles, delivery, price, and next suggestion, without making changes. Use it to review current subscription status safely.

Instructions

Equivale a wetaca subscription show. Suscripción completa: perfiles, entrega, precio y próxima sugerencia. 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_subscription_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?

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Solo lectura' merely restates structured data. The one genuine addition beyond annotations is the enumeration of what the response contains (profiles, delivery, price, next suggestion), which matters because there is no output schema; however, nothing is said about behavior when no subscription exists or when auth/profile is missing.

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 compact clauses with the tool's identity first and the returned payload front-loaded; no filler. The CLI-equivalence clause is marginally redundant with the tool name but is cheap and aids discoverability.

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 read tool with a fully documented schema and no output schema, the definition covers purpose and return contents adequately. The remaining gaps — session/auth assumptions and empty-state behavior — are minor, though the latter would help an agent interpret a bare or failing response.

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 carries no burden here. It adds no meaning beyond the schema, which is the baseline-3 case for fully documented parameters.

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 precisely what is returned — 'Suscripción completa: perfiles, entrega, precio y próxima sugerencia' — and anchors it to the CLI command `wetaca subscription show`. It reads clearly as a read of the current subscription, distinguishable from the mutation siblings (pause/resume) and from the narrower profiles/suggestion tools, though it never explicitly names those alternatives.

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: an agent can infer 'call this to see the current subscription' from the payload listing, but there is no explicit when-to-use statement, no mention of prerequisites (e.g. authenticated session, profile selection), and no named alternative for narrower queries.

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