Skip to main content
Glama
chandshy
by chandshy

Cancel Reminder

cancel_reminder
Idempotent

Cancel a pending no-reply reminder by ID. Returns false if the reminder ID is unknown or already fired.

Instructions

Cancel a pending no-reply reminder by ID. Silently returns false if the ID is unknown or the reminder already fired.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reminder_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYes
messageIdNo
reasonNo
Behavior4/5

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

Annotations already indicate idempotency; the description adds that it silently returns false if the ID is unknown or the reminder already fired, providing helpful behavioral context beyond annotations.

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?

The description is a single sentence that efficiently covers the action and return behavior, with no redundant text.

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 simple tool with one parameter and clear annotations, the description is fairly complete. It could mention where to obtain the reminder ID, but it's adequate.

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

Parameters2/5

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

The parameter is only named 'reminder_id' with no schema description (0% coverage). The description mentions 'by ID' but adds no details on format, source, or constraints.

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?

The description clearly states it cancels a pending no-reply reminder by ID, distinguishing it from other reminder tools like check_reminders or list_pending_reminders.

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?

The description implies usage when you have a reminder ID to cancel, but does not explicitly mention when not to use it or suggest alternatives like list_pending_reminders to obtain the ID.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chandshy/mailpouch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server