Skip to main content
Glama
chandshy

mailpouch

by chandshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check Reminders

check_reminders

Retrieve all pending reminders that have passed their deadline, mark them as fired, and enable the agent to search INBOX for replies before deciding to surface them.

Instructions

Return every pending reminder whose deadline has passed. Each returned reminder is transitioned to 'fired' status so it won't appear in subsequent calls. The agent can then search INBOX for replies to messageId and decide whether to surface the reminder to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
firedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional 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).",
+  "type": "string"
+}
  2. First observedv3.0.77

TDQS

A4/5.0
Behavior4/5

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

Annotations show readOnlyHint=false, idempotentHint=false, destructiveHint=false. Description adds context by disclosing the transition to 'fired' status and that reminders won't appear in subsequent calls, which is consistent. Provides behavioral context beyond annotations without contradiction.

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 sentences, highly concise and front-loaded with core action. Every sentence adds value: action, side effect, and follow-up guidance. No wasted words.

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?

Given the presence of an output schema (not shown), the description adequately covers purpose, side effects, and next steps. It could mention that the tool returns the reminders, but the output schema likely handles that. Overall, complete for a tool with few parameters and no nested objects.

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

Parameters3/5

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

Schema description coverage is 100% for the only parameter (account_id) with a clear description. Tool description does not add further information about the parameter, so baseline score of 3 is appropriate.

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?

Description clearly states verb 'return' and resource 'pending reminders whose deadline has passed'. It distinguishes from siblings like 'list_pending_reminders' by explaining the transition to 'fired' status, making it specific 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 Guidelines3/5

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

Description implies usage for checking overdue reminders and suggests follow-up action (search inbox), but does not explicitly state when to use this tool versus alternatives like 'list_pending_reminders' or 'cancel_reminder'. Lacks exclusions or comparative guidance.

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

Deploy Server

Other Tools