Skip to main content
Glama
Life Admin MCP

Life Admin MCP

by NKC27

Export to calendar

export_calendar
Idempotent

Export due-date items to an .ics file for Apple, Google, or Outlook calendars, creating all-day events with reminders and repeating events; re-import after changes to update them.

Instructions

Write every item that has a due date to an .ics file the user can import into Apple Calendar, Google Calendar or Outlook. Each item becomes an all-day event with a 9am reminder when its reminder window opens and another on the day; repeating items repeat in the calendar. After changes, export again and import into the same calendar to update the events. Provider and cost are included unless minimal is true; references and notes never are. Calendars often sync to a cloud account, so tell the user that.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
minimalNoLeave out provider and cost (titles and dates only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (write operation, idempotent), it discloses the output format (.ics), event shape (all-day with 9am reminder when the reminder window opens plus one on the day), repeat handling, and the update-by-re-import semantics. It also states what is included (provider, cost) versus never included (references, notes) and warns that calendars sync to a cloud account — context an agent could not derive from structured fields.

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?

Four sentences, front-loaded with the core action and artifact, then behavior, then update workflow, then a privacy caution. Nearly everything earns its place, though the reminder/inclusion detail is dense and could be marginally tightened.

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 zero-required-parameter export tool with no output schema, it covers format, content, reminders, repeats, and update flow. The one gap is that it never says how the agent receives the .ics file (path, inline content, or download link), which matters precisely because there is no output schema.

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% and the only parameter, `minimal`, is already documented in the schema. The description restates it as 'provider and cost are included unless `minimal` is true', which clarifies the effect but adds little beyond the schema's own wording.

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 states a specific verb and concrete artifact: writing every dated item to an .ics file importable into Apple Calendar, Google Calendar, or Outlook. It names the exact content mapped (items with a due date) and how each item is rendered, leaving no ambiguity about what the tool produces.

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?

It gives clear context for use (calendar export/import into a user's calendar) and an explicit re-use rule: after changes, export again and import into the same calendar to update events. It lacks an explicit 'do not use when' or a named alternative, but sibling tools offer no competing calendar-export path.

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