Skip to main content
Glama

Listar perfiles

wetaca_profiles_list
Read-onlyIdempotent

List Wetaca subscription profiles to retrieve each profile's ID, name, and menu; read-only access for reviewing account profiles.

Instructions

Equivale a wetaca profiles list. Perfiles de la suscripción (id, nombre, menú). 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_profiles_list"
  }
}

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

B3.2/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; 'Solo lectura' merely restates the read-only hint rather than adding context. The one piece of added value is disclosing the returned fields (id, nombre, menú), though pagination, empty results and auth requirements are not covered.

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 fragments with the CLI equivalence front-loaded and zero filler. Nothing needs to be cut, though the fragmentary style leaves no room for the guidance that is missing.

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 read-only list with no output schema, two fully documented generic parameters and full annotation coverage, the description supplies enough to call it correctly. It could be more complete by noting what an empty profile list looks like, but nothing essential is absent.

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?

Both parameters (debug, profile) have 100% schema description coverage, so the schema already explains them fully, and the description adds nothing about them. Baseline 3 applies when the schema does the heavy lifting and the description stays silent.

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 (perfiles de la suscripción) and the returned fields (id, nombre, menú), and anchors it to the CLI equivalent `wetaca profiles list`, so the verb 'list' is unambiguous. It does not explicitly contrast with the pause/resume profile siblings, but the read-only list scope is clear enough to separate it from those mutations.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives among the many sibling list tools (addresses, menu, orders, vouchers) or the profiles_pause/resume tools. Usage is only implied by the tool name and the CLI-equivalence note.

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