Retrieve all reminders scheduled via natural language, covering both active and pending deliveries through Slack or Telegram.
Get all reminders
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": "get-reminders"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Get all reminders' without detailing scope (e.g., user-specific or system-wide), performance implications, or whether completed/deleted reminders are included. This lack of transparency could mislead the agent about the tool's behavior.
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?
The description is extremely concise at two words, which is appropriate for a simple tool with no parameters. It front-loads the key information, and every word earns its place. However, it could benefit from a bit more context without sacrificing brevity.
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?
Given the lack of output schema and annotations, the description is incomplete. It does not clarify what 'all' means—whether it is all reminders for the current user, all across the system, or includes expired or deleted reminders. The agent may need additional context to use this tool correctly.
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?
The input schema has no parameters (100% coverage), and the description does not need to add parameter semantics. The baseline for zero parameters is 4, and the description adds no value beyond the schema, which is acceptable.
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?
The description 'Get all reminders' clearly states the verb (Get) and resource (reminders). It distinguishes itself from sibling tools like create-reminder and delete-reminder as a retrieval operation, and from get-current-time as dealing with reminders.
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?
The description implies usage for retrieving all reminders, but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context suggests it's the only retrieval tool for reminders, so usage is implied but not clearly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.