Skip to main content
Glama
codefuturist

Email MCP Server

by codefuturist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create reminder

create_reminder

Create a macOS Reminders task from an email, with a deep link back to the source message in Mail.app. Use for turning email action items, deadlines, and follow-ups into reminders.

Instructions

Create a reminder in macOS Reminders.app from an email. Shows a native confirmation dialog before adding. The reminder notes include a message: deep link that reopens the source email in Mail.app. Use for action items, deadlines, and follow-up tasks extracted from emails. Use analyze_email_for_scheduling first to let the AI decide if a reminder is appropriate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoReminder body/notes (defaults to auto-built from email; an open-email deep link is appended either way)
titleNoReminder title (defaults to email subject)
accountYesEmail account name
confirmNoShow native confirmation dialog before adding (default: true)
mailboxNoMailbox containing the emailINBOX
due_dateNoISO 8601 due date (e.g. 2026-02-20T10:00:00). Leave empty for no due date.
email_idYesEmail ID from list_emails_metadata
priorityNoReminder prioritynone
list_nameNoReminders list name (default list if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / notes / description
      Previous value: -"Reminder body/notes (defaults to auto-built from email)"New value: +"Reminder body/notes (defaults to auto-built from email; an open-email deep link is appended either way)"
  2. First observedv0.2.3

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavior beyond annotations: a native confirmation dialog appears before adding, and notes always get an appended deep link that reopens the source email. It does not state permission/authorization requirements or what happens if the Reminders list is missing, so it falls short of a full behavioral picture.

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?

Four short sentences, each carrying a distinct load: what it does, the confirmation behavior, the notes side effect, and the routing precondition. Front-loaded with purpose and zero filler.

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 9-parameter mutation tool with no output schema, the description covers purpose, side effects, and prerequisites, which is most of what an agent needs. It stops short of describing the result returned or list-not-found failure modes.

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%, so all 9 parameters are already documented. The description mostly restates schema facts (notes auto-built, deep link appended, title defaults to subject) rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb (create), resource (reminder), target app (macOS Reminders.app), and source (an email). An agent can immediately distinguish it from list_reminders and analyze_email_for_scheduling.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('action items, deadlines, and follow-up tasks extracted from emails') and names the gating alternative ('Use analyze_email_for_scheduling first'). This is a concrete when/when-not routing instruction.

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