Skip to main content
Glama

Estado de la sesión

wetaca_auth_status
Read-onlyIdempotent

Check whether the Wetaca CLI session for a profile is valid. If unauthenticated, run wetaca auth login in your terminal; never paste tokens, cookies, or passwords in chat.

Instructions

Equivale a wetaca auth status. Dice si la sesión del perfil es válida. Si authenticated es false o el motivo es auth_required, la persona tiene que ejecutar wetaca auth login en su terminal. No pidas ni pegues tokens, cookies ni contraseñas en el chat. 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_auth_status"
  }
}

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, and the description's 'Solo lectura' merely restates that. It does add real behavioral value by naming the `authenticated` flag and the `auth_required` reason, plus a security constraint not to request or paste tokens, cookies or passwords in chat.

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?

The definition is front-loaded with the CLI equivalence and then the diagnostic outcome, followed by the remediation and the safety rule. Every sentence is short and purposeful, with only minor redundancy in 'Solo lectura' duplicating readOnlyHint.

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 usefully names the fields an agent must branch on (`authenticated`, reason `auth_required`) and the correct next action. It does not enumerate the full return payload, but the essentials for calling and acting on the result are present.

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%, so both `debug` and `profile` are already documented in the schema with their CLI flags and default behavior. The description adds nothing about either parameter, which is acceptable but is the baseline when the schema carries the full load.

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 gives a specific verb and resource: it reports whether the profile's session is valid, and anchors it to the equivalent CLI command `wetaca auth status`. It is clearly a status/read operation and implicitly distinct from `wetaca_auth_logout`, though it never names a sibling to contrast with.

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

Usage Guidelines4/5

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

It gives a concrete decision rule: if `authenticated` is false or the reason is `auth_required`, the user must run `wetaca auth login` in their own terminal. That is strong remediation guidance, but there is no explicit statement of when to prefer this over other session-related siblings such as `wetaca_me` or `wetaca_doctor`.

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