Skip to main content
Glama

update_settings

DestructiveIdempotent

Cambia ajustes, sólo los que se pasan (lo demás queda igual). Las mismas reglas que la pantalla de Ajustes: · avisos: { reminders, recaps, tasks, shares, calendar, colgados, colgados_reunion, colgados_weekends, informe_vos } → true prende, false apaga. minutos_antes_de_eventos (hasta 5), hora_de_lo_pendiente "HH:MM", informe_vos_dias 7 | 15 | 30. · idioma es | en, tema_oscuro dark-blue | dark-gray | black, pomodoro { foco_min, descanso_min }. · Del workspace (dueño o admin): zona_horaria (IANA), cierre_automatico, digest { activo, hora "HH:MM" en la zona de la persona, tipo daily | weekly | monthly, sin_fines_de_semana }. Confirmá con la persona antes de apagar avisos. Devuelve cómo quedó todo.

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": "update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
avisosNotrue prende, false apaga
digestNo
idiomaNo
pomodoroNo
tema_oscuroNo
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
zona_horariaNoZona IANA del workspace, p. ej. America/Argentina/Buenos_Aires
informe_vos_diasNo
cierre_automaticoNoCerrar solos los días pasados del Daily
hora_de_lo_pendienteNoHora local del aviso diario de lo que requiere atención, HH:MM
minutos_antes_de_eventosNoMinutos antes de cada evento con hora, p. ej. [10] o [60, 10]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, and the description goes beyond them by disclosing merge semantics (unsent fields stay untouched), a permission gate for workspace settings, a confirmation requirement, and that it returns the resulting state. This adds real value rather than restating the flags.

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?

Front-loaded one-liner followed by grouped bullets that mirror the payload structure, so an agent can scan to the field group it needs. Slight waste in re-listing enum values already present in the schema.

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?

No output schema exists, and the description compensates by stating it returns the final state of everything. Combined with patch semantics, permission scoping, and the confirmation rule, an agent has enough to call this correctly across 11 parameters and nested objects.

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?

At 55% schema coverage the description does meaningful work: it clarifies that digest.hora is interpreted in the person's own timezone, that zona_horaria expects IANA names, and that minutos_antes_de_eventos accepts up to 5 minute offsets. Some enum listings duplicate the schema, but the semantic hints (timezone interpretation, admin-scoped fields) are not in the schema.

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?

"Cambia ajustes, sólo los que se pasan (lo demás queda igual)" states a specific verb and resource plus patch semantics, which immediately separates it from a read counterpart like get_settings. It does not name a sibling explicitly, but the operation is unambiguous.

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?

Gives concrete conditions: workspace-level fields are restricted to owner/admin, and the agent must confirm with the person before turning notifications off. It never spells out "use this instead of get_settings when…", but the implied read/write split is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources