ReminderIt

Edit reminder

update_reminder

DestructiveIdempotent

Edit a reminder's wording or schedule. Only the fields you pass are changed.

Use for "move it to 7am", "say it differently", "stop after the 20th". To pause or
resume, use pause_reminder / resume_reminder. To change the voice, use
set_reminder_voice. To skip particular dates, use set_skip_dates.

Args:
    reminder_id: Reminder to edit (from list_reminders).
    title: New short label.
    message_text: New spoken message (written as natural speech, max 600 chars).
    cron_expr: New cron schedule, e.g. "0 7 * * *" for daily 7am.
    interval_days: New "every N days" interval (1-365).
    run_at: New ISO 8601 datetime for a one-off reminder.
    timezone: New IANA timezone. Changing this moves every future call.
    start_date: New ISO start date for a recurring series.
    end_date: New ISO end date; the series stops after it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	No
`run_at`	No
`end_date`	No
`timezone`	No
`cron_expr`	No
`start_date`	No
`reminder_id`	Yes
`message_text`	No
`interval_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.8/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 non-obvious behavioral context: partial updates (unspecified fields untouched), that changing timezone 'moves every future call', and that the series stops after end_date. It does not explain what the destructiveHint implies (e.g., whether an edit can clobber existing schedule state), which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the key partial-update guarantee, then a routing sentence, then a scannable Args block. Given 9 parameters, the length is justified and no sentence is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. With usage routing, partial-update semantics, and full parameter documentation, an agent has everything needed to call this mutation correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full parameter burden — and it does: every one of the 9 params is documented with format and meaning, including a cron example, the 1-365 interval bound, the 600-char message limit, ISO date expectations, and the source of reminder_id (list_reminders).

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?

States a specific verb and resource ('Edit a reminder's wording or schedule') and immediately clarifies the partial-update semantics with 'Only the fields you pass are changed.' An agent can distinguish this from create_reminder, delete_reminder, and the pause/resume siblings without opening a 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?

Provides explicit user-phrase triggers ('move it to 7am', 'say it differently', 'stop after the 20th') plus three named alternatives with the condition that selects each: pause_reminder/resume_reminder, set_reminder_voice, and set_skip_dates. This is exactly the when/when-not/alternatives pattern.

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

All ReminderIt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?