Skip to main content
Glama

update_reminder

Destructive

Mueve un recordatorio a otra hora: el «posponer» del aviso, o cambiarlo de día. Mueve las cuatro piezas a la vez (la línea de la nota, su segmento, el aviso del cron y la tarea si colgaba de una), como el botón de la app; sin eso la nota deshace el cambio.

Dos formas: `snooze_minutes` ("posponelo 30 minutos", desde ahora) o
`date` y/o `time` ("pasalo a mañana a las 9"; lo que falta queda como
estaba). Hora en la zona del usuario. Funciona también con uno que ya sonó:
vuelve a quedar pendiente. Para darlo de baja, cancel_reminder.

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": {
      "reminder_id": "<reminder_id>"
    },
    "name": "update_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoNuevo día, YYYY-MM-DD
timeNoNueva hora, 'HH:MM'
reminder_idYesID del recordatorio (de get_reminders)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
snooze_minutesNoPosponer tantos minutos desde ahora (máx. 24 h)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real behavior the annotations cannot: the move must propagate to four coupled pieces (note line, its segment, cron alert, linked task) or the note reverts the change. It also discloses the timezone basis and the state transition back to pending. It stops short of saying whether the change is undoable or what the response contains, which keeps it below a 5 for a destructive mutation.

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 paragraphs, front-loaded with the core action and then the two calling forms, so an agent reading only the first line still knows what to do. The parenthetical enumeration of the four pieces is dense but justified because it explains the failure mode. Minor redundancy between the opening line and the two-forms paragraph.

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 5-parameter mutation with no output schema, the description covers the semantics, side effects, timezone, and state transitions an agent needs to invoke it correctly. The remaining gap is that, with no output schema, nothing tells the agent what a successful move returns.

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 earns above that by explaining the interaction between parameters — that `snooze_minutes` is measured from now, that `date` and `time` may be supplied independently, and that omitted fields retain prior values, plus the user-timezone interpretation. The only parameter it never touches is `workspace_id`, whose semantics live entirely in the schema.

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?

Opens with a specific verb+resource ("Mueve un recordatorio a otra hora") and immediately disambiguates the two senses the tool covers: snooze the alert or move it to another day. An agent can distinguish it from cancel_reminder or update_task without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing in both directions: two call forms (`snooze_minutes` relative-from-now vs `date`/`time` absolute, with unset fields preserved), and names the alternative for the adjacent intent ("Para darlo de baja, cancel_reminder"). It also covers the edge case of a reminder that already fired, which changes whether the agent should reach for this tool at all.

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