Skip to main content
Glama
codefuturist

Email MCP Server

by codefuturist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add to calendar

add_to_calendar

Create a local calendar event from an email by extracting ICS attachments, meeting links, dial-in details, attendees, and body text, then saving linked attachments.

Instructions

Add an email event to the local calendar (macOS Calendar.app / Linux via xdg-open). Automatically extracts event data from the email: ICS attachments, meeting URL (Zoom/Teams/Meet), conference dial-in / ID / passcode, attendees, and email body excerpt. All relevant email attachments (PDFs, docs, etc.) are saved locally and linked in the event notes. A native confirmation dialog is shown on macOS before the event is written. Returns one of: added | cancelled | timed_out | no_display.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYesAccount name
confirmNoShow native confirmation dialog before adding (default: true)
mailboxNoMailbox path (default: INBOX)INBOX
email_idYesEmail UID
alarm_minutesNoMinutes before event to show an alert (default: 15)
calendar_nameNoTarget calendar name (empty = default calendar)
save_attachmentsNoSave non-ICS email attachments locally and link them in the event notes (default: the [settings.attachments] auto_download setting)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
    • removedInput schema / properties / save_attachments / default
      Removed value: -true
    • changedInput schema / properties / save_attachments / description
      Previous value: -"Save non-ICS email attachments locally and link them in the event notes"New value: +"Save non-ICS email attachments locally and link them in the event notes (default: the [settings.attachments] auto_download setting)"
  2. First observedv0.2.3

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint=false/destructiveHint=false annotations: it discloses that a native confirmation dialog gates the write on macOS, that non-ICS attachments are written to local disk and linked in notes, that platform behavior differs (Calendar.app vs xdg-open), and it enumerates every return outcome including cancelled and timed_out.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense, front-loaded paragraph with no filler; the verb and platform lead, followed by extraction behavior, side effects, and return values. Slightly long, but every clause carries information an agent needs.

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?

With 7 parameters and no output schema, the description compensates by enumerating the four possible return values and describing the side effects (attachment writes, confirmation dialog, platform dispatch). Nothing needed to call it correctly is missing.

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?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning: it clarifies that confirm maps to a macOS-native dialog before the write, and that save_attachments covers any non-ICS attachment with local persistence plus note linking. alarm_minutes and calendar_name are left to the schema.

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 and resource — 'Add an email event to the local calendar' — and names the underlying platform (macOS Calendar.app / Linux via xdg-open). This clearly separates it from siblings like extract_calendar, analyze_email_for_scheduling, and create_reminder, which do not write to the calendar from an email.

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 implicit context (an email containing event data) is conveyed through the extraction behavior, so an agent can infer when to reach for it. However, it never explicitly names alternatives such as extract_calendar or analyze_email_for_scheduling, nor states when NOT to use this tool.

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