Skip to main content
Glama

Editar el menú

wetaca_suggestion_edit
Destructive

Change the tuppers in a profile's next-week suggestion by specifying product IDs and quantities. Runs as a dry run by default; set confirm to apply the change.

Instructions

Equivale a wetaca suggestion edit --profile-suggestion ID --set "id:cantidad,...". Cambia los tuppers de un perfil en la próxima semana. Los ids salen de wetaca_suggestion_show o wetaca_menu_list. set es una lista productId:cantidad separada por comas; la cantidad es un entero ≥ 0. Por defecto --dry-run (devuelve wouldSend y no cambia el menú). confirm:true envía --yes. resume opcional se traduce a --resume=true|false, igual que 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": {
      "profile_suggestion": "<profile_suggestion>",
      "set": "<set>"
    },
    "name": "wetaca_suggestion_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
setYesPares productId:cantidad, por ejemplo "123:2,456:1".
debugNoSi es true, wetaca escribe en stderr una línea por petición HTTP (--debug). No incluye el token.
resumeNoSi se informa, se pasa --resume=true o --resume=false al CLI.
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.
profile_suggestionYesprofileSuggestionId del perfil dentro de la sugerencia.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, but the description adds the crucial nuance that the default path is --dry-run and returns wouldSend without touching the menu, and that confirm:true maps to --yes. This is exactly the kind of information an agent cannot get from the annotations and prevents accidental mutations.

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?

Dense but every sentence carries a fact: CLI equivalence, effect, id sources, set syntax, dry-run default, confirm and resume mapping. The leading CLI-equivalence clause is slightly less useful than the behavioral facts that follow, but nothing is filler.

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 destructive mutation with no output schema, the definition covers the safety model (dry-run default, wouldSend, confirm) and the id provenance well. It does not describe what a successful real run returns or how partial failures in a multi-item set are handled.

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 the baseline is 3. The description restates the set format (`productId:cantidad`, integer >= 0) and the resume -> --resume=true|false mapping, adding little beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Cambia los tuppers de un perfil en la próxima semana" is a specific verb plus resource plus scope. The description also names the exact source of the ids (wetaca_suggestion_show, wetaca_menu_list), which distinguishes it cleanly from the sibling read/list tools.

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 tells the agent where valid ids come from and that the operation runs as dry-run unless confirm:true is set, which is actionable when-to-use guidance. It stops short of naming an explicit alternative operation (e.g. pause/resume) or stating when not to call it, so it is short of a 5.

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