Skip to main content
Glama

Leer una clave

wetaca_config_get
Read-onlyIdempotent

Reads a Wetaca CLI configuration value by dotted key and masks token values, enabling read-only inspection of settings.

Instructions

Equivale a wetaca config get <clave>. Lee una clave con puntos, por ejemplo defaultProfile. Si la clave acaba en token, el CLI devuelve ***. Solo lectura.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "wetaca_config_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesClave, con puntos si hace falta (config get <clave>).
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavior beyond that: keys are dotted paths, and any key ending in "token" is redacted to *** in the returned value, which an agent could not learn from the schema or annotations.

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 short sentences, front-loaded with the CLI equivalence and ending with the read-only note. The CLI snippet slightly duplicates the schema's own "config get <clave>" text, but nothing is bloat.

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 low-complexity, single-key read with a fully documented 3-parameter schema and complete safety annotations, this is close to sufficient. It does not say what happens when the key is absent, but that is the only material gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description raises it by giving a concrete key example (defaultProfile) and explaining dotted-path syntax for the required `key` parameter, plus the token-masking rule that affects what value comes back.

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?

"Lee una clave con puntos" states a specific verb (read) and resource (a config key), which distinguishes it from the sibling wetaca_config_list that returns many keys. The CLI equivalence reinforces the scope, though no sibling is named explicitly.

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 by "Lee una clave" versus a list tool, but there is no explicit when-to-use/when-not guidance and no pointer to wetaca_config_list or wetaca_config_set as alternatives for other operations.

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