Skip to main content
Glama

Ver configuración

wetaca_config_list
Read-onlyIdempotent

Lists public Wetaca CLI configuration settings without exposing tokens; read-only, so no account changes are made.

Instructions

Equivale a wetaca config list. Configuración pública del CLI. Los tokens no se muestran. 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_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.4/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, so the safety profile is fully covered. The description adds one genuinely new behavioral fact — that tokens are never exposed in the output — but says nothing about which configuration keys appear or whether values reflect the default vs. the selected profile.

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 clauses, front-loaded with the CLI equivalence and followed by the two facts that matter most (public config, tokens hidden, read-only). The CLI-equivalence sentence is somewhat redundant with the tool name but serves as a useful mental map; nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only config reader with full annotation coverage and no output schema, the description is adequate but leaves the returned shape (which config keys, resolved vs. raw values) undefined. Since no output schema exists, a brief mention of what the configuration dump contains 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?

Schema description coverage is 100%: both `debug` and `profile` are documented in the schema, including their CLI flags and default behavior. The description adds no parameter meaning at all, so the baseline 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?

States the resource (CLI public configuration) and the action via the CLI equivalence `wetaca config list`, plus the scope constraint that tokens are excluded. It does not explicitly differentiate itself from the sibling wetaca_config_get, so it stops short of a 5.

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?

The clause 'Solo lectura' implies this is the read path and not the mutation path (wetaca_config_set), and the tokens note implies it is safe for inspection. However, there is no explicit instruction on when to choose this over wetaca_config_get, wetaca_config_path, or wetaca_auth_status.

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