Skip to main content
Glama
chandshy
by chandshy

Remind If No Reply

remind_if_no_reply

Schedule a follow-up reminder for a sent email that fires after a set number of days if no reply is received. Automatically captures the message ID and recipient to ensure timely follow-up.

Instructions

Schedule a follow-up reminder for a message you've sent. Given the IMAP UID of a message in Sent, captures its Message-ID + recipient and fires a reminder after N days. Use check_reminders to retrieve due reminders; list_pending_reminders to audit; cancel_reminder to drop one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoOptional note explaining the reminder
folderNoFolder containing the message (default: Sent). Provide this to avoid UID collisions across folders.
email_idYesIMAP UID of the sent message
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).
after_daysYesDays from the message's send date until the reminder fires (1–365)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
fireAtYes
subjectYes
recipientYes
Behavior4/5

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

Beyond annotations, the description reveals internal behavior: it captures Message-ID and recipient, then fires after N days. This adds meaningful behavioral context beyond the readOnly/destructive hints.

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?

Two concise sentences, no redundancy, front-loaded with key purpose. Every sentence serves a purpose, making it highly efficient.

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?

Given the presence of an output schema, the description fully covers purpose, parameters, and related tools. It provides sufficient context for an agent to select and use the tool correctly.

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?

With 100% schema coverage, the description adds value by explaining the IMAP UID purpose, folder collision avoidance, account routing, and day range. This supplements the schema definitions effectively.

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 the tool schedules a follow-up reminder for a sent message using its IMAP UID. It differentiates from sibling tools like check_reminders, list_pending_reminders, and cancel_reminder, making the purpose distinct and unambiguous.

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

Usage Guidelines4/5

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

The description explains the input requirements (IMAP UID, days) and mentions related tools for lifecycle management. It lacks explicit 'when not to use' guidance but provides adequate context for correct usage.

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