Skip to main content
Glama
theluckystrike

mcp-office-suite

by theluckystrike
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Hybrid

Write a calendar invite

ics_create

Create a calendar .ics file for a meeting event, specifying title, start time, timezone, duration, location, and attendees.

Instructions

Call this tool to write a .ics calendar file for one meeting. Returns the path written and the meeting time in UTC and in the zone you gave.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gapNoWhat to do with a time that does not exist because the clocks jumped forward: 'forward' takes the time after the jump, 'backward' the time before it. Without this, such a time is refused.
foldNoWhich occurrence of a time that happens twice because the clocks went back. Default 'first'.
zoneYesPlace the start time is given in
startYesStart time, read in `zone` unless it carries an offset
titleYesEvent title
locationNoWhere, or a meeting link
out_pathNoWhere to write the .ics file; default meeting.ics in the data dir. Times are stored in UTC, so the invite lands at the right local time in every attendee's calendar with no time zone block to go stale
attendeesNoAttendees. An entry with an email is invited (ATTENDEE:mailto:...); a name with no email is listed in the description instead, because a calendar cannot invite a name.
descriptionNoBody text
organizer_nameNoYour display name for the ORGANIZER line
organizer_emailNoYour email address, written as the ORGANIZER so replies have somewhere to go. Leave it out and your shared business profile's email is used; with neither, the ORGANIZER line is omitted rather than filled with an address you improvised
duration_minutesYesLength in minutes, at most 1440

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight. It does disclose the main side effect (writing a file) and the return values (path and meeting time). However, it does not mention overwrite behavior, whether invites are sent, error handling, or DST edge cases, which leaves important behavior implicit.

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 sentences with no filler. The purpose is front-loaded and the return information is concise and useful. Every word earns its place.

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?

For a 12-parameter tool with no annotations and no output schema, the description is minimal but adequate. The rich schema covers parameter details, but the description lacks explicit sibling differentiation, overwrite/safety behavior, and a fuller picture of the return format.

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 the schema already documents all parameters thoroughly. The description adds no parameter-level meaning beyond saying the meeting time is returned in UTC and the provided zone, which is output behavior rather than parameter semantics.

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 action — write a .ics calendar file for one meeting — and clearly identifies the resource. This distinguishes it from nearby siblings like ics_import and event_export, since the focus is on creating a single .ics file.

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 gives clear context for when to call the tool: write a .ics calendar file for a single meeting. It does not explicitly name alternatives or when-not conditions, but the intended use case is unambiguous despite the large sibling set.

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

Install Server

Other Tools