Skip to main content
Glama

Cambiar configuración

wetaca_config_set
DestructiveIdempotent

Writes a configuration key and value to config.json without prompting. Keys ending in token are rejected; pass confirm=true to apply the change.

Instructions

Equivale a wetaca config set <clave> <valor>. Escribe config.json. El CLI no pregunta y rechaza las claves que acaban en token (el token solo entra con wetaca auth login). Este servidor no llama al CLI hasta que confirm sea true. Los valores true y false se guardan como booleanos, igual que en el CLI.

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>",
      "value": "<value>"
    },
    "name": "wetaca_config_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesClave a escribir. No puede acabar en token.
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
valueYesValor. true y false se convierten en booleanos.
confirmNoPor defecto false: no hay efectos en la cuenta. true equivale a --yes y ejecuta la operación. Úsalo solo si la persona pidió exactamente esta operación y ya vio el resumen.
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.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds behavior they cannot express: the CLI never prompts, token-suffixed keys are refused outright, the server performs no side effects until confirm is true, and booleans are persisted as real booleans rather than strings. What it omits is failure/overwrite semantics — whether an existing key is replaced, and what happens if the profile does not exist.

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 so the agent can anchor the operation immediately. Minor redundancy: the boolean-conversion and token-key facts also appear in the schema, so one clause could be dropped without loss.

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 five-parameter mutating tool with no output schema and annotations that already flag destructiveness, the description supplies the missing pieces an agent needs: the dry-run confirm gate, the token-key refusal, and the CLI equivalence. It stops short of describing failure modes or whether writing a non-existent key creates it, which would matter for a destructive write.

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 every one of the five parameters is already documented in the schema, including the token-key restriction, boolean conversion, and the confirm gate. The description restates those same points rather than adding new meaning (e.g. which keys are valid, format expectations for value). Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"Equivale a `wetaca config set <clave> <valor>`. Escribe config.json." gives a specific verb (set) and a concrete resource (config.json key/value), so the agent knows exactly what mutates and where. It does not name config_get or config_list as the read-only counterparts, so sibling differentiation is inferred from the operation name rather than stated.

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 carves out an explicit exclusion (keys ending in "token" are rejected) and routes that case to an alternative ("el token solo entra con `wetaca auth login`"). It also states the confirm gate before any CLI call, which tells the agent the call is inert by default. It lacks an explicit "use wetaca_config_get to read a value first" pointer, but the when/when-not conditions are clear.

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