Skip to main content
Glama

Saldo del monedero

wetaca_wallet_show
Read-onlyIdempotent

Retrieves your Wetaca wallet balance in cents and euros via a read-only call, so you can check available credit without topping up or making payments.

Instructions

Equivale a wetaca wallet. Saldo del monedero, en céntimos y en euros. Solo lectura. No recarga el monedero ni gestiona pagos.

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_wallet_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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description is consistent with them ('Solo lectura'). It adds real value beyond the annotations by describing the returned units (cents and euros) and by explicitly bounding scope away from recharges and payments, which matters since there is no output schema.

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 no waste; the CLI equivalence and the core purpose are front-loaded, and the exclusions follow. Slightly terse, but every sentence carries information.

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 no output schema, the description supplies the essentials: what is returned and in which units, plus what the tool will not do. Nothing an agent needs to invoke it correctly appears to be missing.

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 generic CLI plumbing already documented in the schema. The description adds no meaning about them, which is acceptable at full coverage but earns no credit above baseline.

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 the resource (wallet balance) and the exact values returned (cents and euros), and maps it to the CLI command `wetaca wallet`. It does not name a sibling tool, but the negative scoping ('no recarga el monedero ni gestiona pagos') separates it from any top-up or payment tool.

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 implied rather than stated: an agent learns to call it to read the balance, and learns it must not use it for top-ups or payment management. No alternative tool is named for those excluded cases, so routing guidance is only partial.

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