Skip to main content
Glama

Set reminder

set_reminder
Idempotent

Give a todo a due time and a reminder, or take it off (clear: true). due_at is a time like 2026-11-20T09:00 in the user's time zone, or with an offset (2026-11-20T09:00:00+01:00). By default the reminder comes in the app at the due time; remind_before moves it earlier, and email or telegram send it there too.

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": {
      "todo": "<todo>"
    },
    "name": "set_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoRemind in the app. Default true.
todoYesThe todo. Its id (from any other tool's output) or its exact title.
clearNotrue removes the reminder.
emailNoAlso by email.
due_atNoWhen it is due.
telegramNoAlso on Telegram, if the user linked it.
remind_beforeNoMinutes before due_at to remind. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutation is non-destructive and idempotent, and the description adds genuinely new behavior: the default is an in-app reminder fired exactly at due_at, remind_before shifts it earlier, and email/telegram fan it out to other channels. Undisclosed edge cases remain, such as what happens when clear: true is sent with no existing reminder or when the todo title matches multiple todos.

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?

Three sentences, each doing distinct work: the core action plus clear mode, then the due_at format, then channel and remind_before defaults. The action is front-loaded and no sentence is filler despite the parenthetical packing.

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 7-parameter mutation tool with no output schema, the description covers the modes, defaults, timestamp format, and notification channels — enough to call it correctly on the first try. The remaining gap is failure semantics (unresolvable todo title, clearing a non-existent reminder) and confirmation of what the call 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 schema baseline already carries the parameters. The description still earns credit by specifying the due_at wire format with two literal examples including an offset, and by explaining the default app=true-at-due-time interaction that the schema's one-line field descriptions do not convey.

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?

The description states a concrete verb and resource pair — attach a due time and reminder to a todo, or remove it with clear: true. There is no ambiguity about what gets written. It never names a sibling (e.g. list_reminders as the read counterpart), so differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

It covers the two in-tool modes well: setting a reminder versus clearing it with clear: true. What is missing is when to reach for this instead of the read-side sibling, or any prerequisite such as the todo already needing to exist. Usage is implied by the description rather than stated as guidance.

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