Send Out

Create calendar event

create_calendar_event

Read-onlyIdempotent

Builds one calendar event the user adds themselves. Use when the user wants to schedule a meeting, send an invite or get an .ics file. Needs title and start. start is YYYY-MM-DD for an all-day event or YYYY-MM-DDTHH:MM for a timed one; a timed start also needs timezone (such as Europe/Paris) or a Z or offset like +07:00. Set end or duration_minutes (default 60 minutes). Returns a Google Calendar link and .ics text that imports into any calendar app. Nothing is stored and no calendar is changed until the user saves the event.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	No	Optional end in the same format as start, such as "2026-11-02T10:30". For an all-day event, the last day, such as "2026-11-04".
`start`	Yes	Start as YYYY-MM-DD for an all-day event, such as "2026-11-02", or YYYY-MM-DDTHH:MM for a timed event, such as "2026-11-02T09:30". A timed start needs timezone, or a Z or offset at the end such as "2026-11-02T09:30+07:00".
`title`	Yes	Event title, such as "Sprint Review".
`filename`	No	Optional .ics filename (without or with .ics).
`location`	No	Meeting room, street address, or video call URL.
`timezone`	No	IANA time zone name in Area/City form, such as America/New_York, Europe/Paris or Asia/Tokyo. Needed for a timed start that has no Z or offset.
`description`	No	Event agenda, notes, or participant details.
`duration_minutes`	No	Duration in minutes if end date-time is omitted (for example, 30 or 60).
`reminder_minutes`	No	Minutes before the event to trigger an alarm/reminder (for example, 10 or 15).

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes	Short notes to pass on to the user, including any warning.
`status`	Yes	Always ok when the event was built. Bad input returns an error instead.
`warning`	No	Warning if URL exceeds safe limits.
`filename`	Yes	Suggested file name for the .ics file.
`url_length`	Yes	Length of the Google Calendar URL.
`ics_content`	Yes	RFC 5545 iCalendar (.ics) formatted calendar text.
`google_calendar_url`	Yes	Google Calendar web intent link with pre-populated fields.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedInput schema / examples

Added value: +[
+  {
+    "duration_minutes": 60,
+    "start": "2026-11-15T14:00",
+    "timezone": "Europe/London",
+    "title": "Product Launch"
+  }
+]

Changed8 schema fields changedOct 11, 2026

changedInput schema / properties / end / description

Previous value: -"Optional end date or date-time in the same format as start."New value: +"Optional end in the same format as start, such as \"2026-11-02T10:30\". For an all-day event, the last day, such as \"2026-11-04\"."

addedInput schema / properties / end / pattern

Added value: +"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2})?(Z|[+-]\\d{2}:\\d{2})?)?$"

changedInput schema / properties / start / description

Previous value: -"Start date (YYYY-MM-DD for all-day) or start date-time (YYYY-MM-DDTHH:MM, add Z, offset, or timezone)."New value: +"Start as YYYY-MM-DD for an all-day event, such as \"2026-11-02\", or YYYY-MM-DDTHH:MM for a timed event, such as \"2026-11-02T09:30\". A timed start needs timezone, or a Z or offset at the end such as \"2026-11-02T09:30+07:00\"."

addedInput schema / properties / start / pattern

Added value: +"^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2})?(Z|[+-]\\d{2}:\\d{2})?)?$"

changedInput schema / properties / timezone / description

Previous value: -"IANA time zone name (such as America/New_York, Europe/Paris, Asia/Tokyo)."New value: +"IANA time zone name in Area/City form, such as America/New_York, Europe/Paris or Asia/Tokyo. Needed for a timed start that has no Z or offset."

changedInput schema / properties / title / description

Previous value: -"Event title or meeting name."New value: +"Event title, such as \"Sprint Review\"."

addedOutput schema / properties / notes / description

Added value: +"Short notes to pass on to the user, including any warning."

addedOutput schema / properties / status / description

Added value: +"Always ok when the event was built. Bad input returns an error instead."

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, but the description adds the crucial behavioral fact that despite the "create" name nothing is persisted or modified: "Nothing is stored and no calendar is changed until the user saves the event." It also discloses what is returned (a Google Calendar link plus .ics text), which resolves the naming/annotation tension an agent would otherwise have to guess at.

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?

Five short sentences, each carrying distinct load: purpose, trigger, required inputs, date/timezone format rules, and the non-persistence/output guarantee. Front-loaded with the purpose and trigger, with format constraints following, so nothing is padding.

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 9 parameters, full schema coverage, an output schema, and rich annotations, the remaining burden on the description is small, and it still covers the ambiguous points: timezone coupling, all-day vs timed format, default duration, and the no-write guarantee. Nothing an agent needs to invoke 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; the description earns above that by stating cross-parameter logic the schema only implies piecewise — a timed start requires timezone or an offset, and "Set end or duration_minutes (default 60 minutes)" supplies the default that no schema field documents. It still does not cover reminder_minutes or filename behavior, so it is not exhaustive.

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 ("Builds one calendar event") and immediately scopes it with "the user adds themselves," which separates it from write-style siblings like create_markdown_file or create_obsidian_note. An agent can identify the artifact produced (Google Calendar link and .ics text) without opening the schema.

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?

Gives explicit trigger conditions: "Use when the user wants to schedule a meeting, send an invite or get an .ics file." That is clear context for selection, but it names no alternatives or exclusions (e.g. how it differs from draft_email or create_whatsapp_link for coordination tasks), so it falls short of the 5 bar.

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

All Send Out tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.