Skip to main content
Glama

Ruta de la configuración

wetaca_config_path
Read-onlyIdempotent

Returns the file paths of config.json and credentials.json for a Wetaca CLI profile, so you can locate configuration files without exposing secret contents.

Instructions

Equivale a wetaca config path. Rutas de config.json y credentials.json. No devuelve el contenido de los secretos. 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_config_path"
  }
}

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, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: it explicitly discloses that secret contents are never returned, which prevents a doomed attempt to read credentials through this tool.

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 very short, front-loaded sentences with no filler; the substance (what paths, no secrets, read-only) comes early. The CLI-equivalence line is the only mildly redundant element, though it helps agents already familiar with wetaca-cli.

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-only lookup with no output schema, the description says what is returned (the two file paths) and what is not (secret contents). Only the shape of the returned object is left unspecified, which is a minor 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?

Schema description coverage is 100% and both optional parameters (debug, profile) carry their own descriptions, including the note that debug output excludes the token. The description adds nothing about either parameter, 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 states a specific payload: the file paths of config.json and credentials.json, plus the CLI command it mirrors (`wetaca config path`). This distinguishes it in substance from wetaca_config_get, but that sibling is never named, so the differentiation is implicit rather than explicit.

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?

There is no explicit when-to-use or when-not-to-use statement, and no named alternative. However, 'No devuelve el contenido de los secretos' implicitly tells the agent that if it needs the actual values it must reach for a different tool (e.g. wetaca_config_get), which is a usable but indirect signal.

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