create_reminder
Add a new reminder to your Reminders.app to manage tasks and deadlines.
Instructions
Creates a reminder in Reminders.app.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Add a new reminder to your Reminders.app to manage tasks and deadlines.
Creates a reminder in Reminders.app.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description only states the basic action. It does not disclose what happens upon creation (e.g., default fields, errors, or response).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded, and to the point. No unnecessary words, but could expand slightly without losing efficiency.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool, the description is adequate but does not explain what fields or data the reminder will have, leaving some ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the schema covers everything. The description does not need to add parameter info, earning the baseline score of 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool creates a reminder in Reminders.app with a specific verb and resource. However, it does not differentiate from sibling tools like update_reminder or create_reminder_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage context is provided; no indication of when to use this tool versus alternatives such as update_reminder or complete_reminder.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'
If you have feedback or need assistance with the MCP directory API, please join our Discord server