Skip to main content
Glama

Diagnóstico

wetaca_doctor
Read-onlyIdempotent

Diagnose Wetaca CLI connectivity by checking Node, api.wetaca.com availability, and active session. Runs a network health check without modifying your account.

Instructions

Equivale a wetaca doctor. Comprueba Node, si api.wetaca.com responde y si hay sesión. Hace una petición de red de diagnóstico. No modifica la cuenta.

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

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, idempotentHint, non-destructive and openWorldHint, so safety is covered structurally. The description still adds real value beyond them by enumerating what the diagnostic inspects (Node, API host reachability, session state) and explicitly confirming 'No modifica la cuenta'. What it does not describe is the shape of the report or how failures are surfaced.

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?

Four short sentences, front-loaded with the CLI equivalence and followed by the concrete checks. No filler or repetition, though the 'Hace una petición de red de diagnóstico' sentence marginally overlaps the api.wetaca.com reachability check.

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?

There is no output schema, so the description carries the burden of telling an agent what the call yields, and it does so by listing the three checks performed. For a zero-required-parameter, read-only diagnostic this is nearly sufficient; a brief note on how results are reported (pass/fail lines vs. exit status) would close the remaining gap.

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?

With schema description coverage at 100%, both parameters (debug, profile) are already fully documented in the schema, including the --debug stderr behavior and the note that the token is not logged. The description adds no parameter meaning of its own, so the baseline of 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 diagnostic scope: it checks Node, whether api.wetaca.com responds, and whether a session exists, and it anchors to the familiar `wetaca doctor` command. That is far more specific than a tautology like 'Diagnóstico'. It stops short of distinguishing itself from wetaca_auth_status, which plausibly also reports session presence, so sibling differentiation is left to inference.

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 can infer this is the troubleshooting entry point when something is misconfigured or connectivity is in doubt. There is no explicit 'use this when X, use auth_status instead when Y' guidance, and no prerequisites or expected failure modes are named.

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