Skip to main content
Glama
Sign In
mail-calendar-mcp

mail-calendar-mcp

by mathewcsims
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calendar_get_event

Read-onlyIdempotent

Retrieve a specific calendar event using its unique iCalendar identifier (UID). Useful for accessing event details after listing events.

Instructions

Get a single event by its uid (stable iCalendar identifier — see calendar_list_events output).

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": {
      "uid": "<uid>"
    },
    "name": "calendar_get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
calendarNameNoCalendar name. Ambiguous if duplicated (common on multi-account setups) — use calendarIndex instead in that case.
calendarIndexNoPosition from calendar_list_calendars, for disambiguating duplicate calendar names. Stable only for the current Calendar.app process.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that the UID is a 'stable iCalendar identifier', providing context about identifier stability. No mention of error handling or missing event behavior.

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?

Single sentence with no wasted words. Front-loaded key information: action, resource, identifier type. Perfectly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not explain the return format or behavior when the event is not found. For a read-only tool, this is a gap; however, annotations indicate idempotent read, mitigating some completeness concerns.

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 67%, with calendarName and calendarIndex having descriptions. The tool description adds minimal value: it notes the UID is from calendar_list_events output, but doesn't elaborate on format or required constraints. Baseline 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?

The description clearly states the tool retrieves a single event by its UID, a specific identifier. It distinguishes from sibling list/search tools by specifying the unique identifier method.

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 mentions using the UID from calendar_list_events output, implying when to use it (when you have a UID). However, it does not explicitly state when not to use it or compare to alternatives like calendar_search_events.

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