Skip to main content
Glama

Resumen de la cuenta

wetaca_me
Read-onlyIdempotent

Retrieve a read-only summary of your Wetaca customer profile, subscription status, and wallet balance; card details are excluded.

Instructions

Equivale a wetaca me. Resumen de cliente, estado de la suscripción y saldo del monedero. Solo lectura. No muestra tarjetas.

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

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's 'Solo lectura' merely restates that, though 'No muestra tarjetas' usefully discloses a data boundary the annotations cannot express. It says nothing about auth requirements, error behavior, or whether the token must be present.

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 with the CLI equivalence first and the negative scope last; nothing is padded. The 'Solo lectura' clause is slightly redundant with the readOnlyHint annotation, costing it a perfect score.

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, zero-required-parameter read tool with full annotation coverage and no output schema, the description gives enough to know what data comes back (client, subscription, wallet). It could be more complete by clarifying how it differs from wetaca_subscription_show, which is the main remaining ambiguity.

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 with their defaults. The description adds no parameter meaning, which is acceptable at full coverage; baseline 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 names a concrete operation and enumerates the payload: client summary, subscription status, and wallet balance, plus a negative scope ('No muestra tarjetas'). It does not explicitly contrast with a sibling such as wetaca_subscription_show, so an agent could still hesitate between them, but the enumerated contents make the resource specific.

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: 'Equivale a `wetaca me`' anchors it to a known CLI command, and 'No muestra tarjetas' hints at what to use when payment cards are needed. There is no explicit when-to-use versus the subscription or orders tools, and no exclusions.

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