Skip to main content
Glama
Sign In
mailpouch

mailpouch

by chandshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cancel Reminder

cancel_reminder
Idempotent

Cancel a pending no-reply reminder by its ID to prevent it from firing. Returns false if the ID is unknown or the reminder has already triggered.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reminder_id": "<reminder_id>"
    },
    "name": "cancel_reminder"
  }
}

Input 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).
reminder_idYes

Output Schema

NameRequiredDescriptionDefault
reasonNo
successYes
messageIdNo

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

A3.9/5.0
Behavior4/5

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

Annotations already indicate non-readOnly (writes), idempotent, and non-destructive. The description adds value by disclosing that 'silently returns false if the ID is unknown or the reminder already fired', which reveals edge-case behavior not captured in 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?

Two efficient sentences front-load the action and add critical behavioral nuance. No redundancy or unnecessary words. Every sentence earns its place.

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 two parameters and an output schema, the description captures the essential behavior and failure cases. It could mention the return type (likely boolean) but is otherwise complete given the low complexity.

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?

Schema coverage is only 50% (account_id has description, reminder_id lacks one). The description does not elaborate on either parameter beyond mentioning the ID in the action. It fails to compensate for the missing schema documentation, leaving the reminder_id parameter semantically underdefined.

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 verb 'Cancel' and the resource 'pending no-reply reminder by ID', specifying both the action and the target. This distinguishes it from sibling 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 use for canceling a specific reminder by ID, but does not explicitly state when to use or not use this tool compared to alternatives. No exclusions or prerequisites are mentioned, but the context is clear enough for its simple purpose.

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