Document Tools

Make a calendar (.ics) file

make_calendar_file

Use this when the user wants a calendar file to import, for example "make a calendar file for this meeting", "create an .ics for my weekly class", "export these dates so I can import them". Input tips: pass 1 to 50 events, each with a title, a start (2026-11-02 for all day, or 2026-11-02T09:30) and an end or duration_minutes, plus timezone (IANA name such as Europe/Paris) for a time without Z or an offset; ask the user for the time zone, never guess it. Example event: {"title":"Sprint review","start":"2026-11-02T09:30","duration_minutes":45,"timezone":"Europe/Paris"}. Optional: location, description, reminder_minutes and recurrence (freq daily, weekly, monthly or yearly, with interval, until or count, and byday). Returns: the .ics text, a download link that works for 24 hours, its expiry and the event count. Not for: adding, changing or reading events in Google Calendar, Outlook or any calendar account; it only makes a file. Errors: status invalid with a message naming the event and field to fix.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`events`	Yes	1 to 50 events, such as [{"title":"Sprint review","start":"2026-11-02T09:30","duration_minutes":45,"timezone":"Europe/Paris"}].
`filename`	No	File name in letters and digits, such as sprint-review; .ics is added.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes	Facts the user should know, such as how long the link works.
`status`	Yes	ok when the file was made; invalid when the input needs a fix (see message).
`message`	No	What to fix in the input when status is invalid.
`filename`	No	Name the download link saves the file as, such as calendar.ics.
`ics_text`	No	The whole .ics file (RFC 5545) when status is ok.
`expires_at`	Yes	When the link stops working (ISO 8601 UTC).
`event_count`	No	Number of events in the file when status is ok.
`download_url`	Yes	Link that works for 24 hours, or null when no link could be made.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedOct 10, 2026

changedInput schema / properties / events / description

Previous value: -"1 to 50 events."New value: +"1 to 50 events, such as [{\"title\":\"Sprint review\",\"start\":\"2026-11-02T09:30\",\"duration_minutes\":45,\"timezone\":\"Europe/Paris\"}]."

addedInput schema / properties / events / items / properties / description / description
```
Added value: +"Optional notes shown in the event body, such as the agenda."
```

changedInput schema / properties / events / items / properties / duration_minutes / description

Previous value: -"Length of a timed event instead of end."New value: +"Length of a timed event in minutes instead of end, such as 45."

changedInput schema / properties / events / items / properties / end / description

Previous value: -"Same format as start. For an all-day event it is the last day, inclusive. Give this or duration_minutes."New value: +"Same format as start, such as 2026-11-02T10:15. For an all-day event it is the last day, inclusive. Give this or duration_minutes."

addedInput schema / properties / events / items / properties / end / pattern

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

addedInput schema / properties / events / items / properties / location / description

Added value: +"Optional place or meeting link shown in the event, such as Room 4B or https://meet.example.com/abc."

addedInput schema / properties / events / items / properties / recurrence / description

Added value: +"Optional repeat, such as {\"freq\":\"weekly\",\"byday\":[\"MO\"],\"count\":10}. In a zone with daylight saving, give until or count."

addedInput schema / properties / events / items / properties / recurrence / properties / freq / description
```
Added value: +"How often it repeats: daily, weekly, monthly or yearly."
```

changedInput schema / properties / events / items / properties / recurrence / properties / until / description

Previous value: -"Last date of the repeat, 2026-12-31."New value: +"Last date of the repeat, such as 2026-12-31. Give until or count, not both."

addedInput schema / properties / events / items / properties / recurrence / properties / until / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

addedInput schema / properties / events / items / 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 / events / items / properties / title / description

Previous value: -"Event title."New value: +"Event title, such as Sprint review."

changedInput schema / properties / filename / description

Previous value: -"File name, letters and digits; .ics is added."New value: +"File name in letters and digits, such as sprint-review; .ics is added."

addedOutput schema / properties / event_count / description

Added value: +"Number of events in the file when status is ok."

addedOutput schema / properties / filename / description

Added value: +"Name the download link saves the file as, such as calendar.ics."

addedOutput schema / properties / ics_text / description

Added value: +"The whole .ics file (RFC 5545) when status is ok."

addedOutput schema / properties / notes / description

Added value: +"Facts the user should know, such as how long the link works."

addedOutput schema / properties / status / description

Added value: +"ok when the file was made; invalid when the input needs a fix (see message)."

changedOutput schema / required

Previous value: -[
-  "status"
-]New value: +[
+  "status",
+  "download_url",
+  "expires_at",
+  "notes"
+]

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.8/5.0

Behavior5/5

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

Beyond the annotations, it discloses the return surface (the .ics text, a download link valid 24 hours, its expiry, event count) and the error contract ('status invalid with a message naming the event and field to fix'). It also adds a hard operational rule not present in annotations: ask the user for the time zone, never guess. Nothing contradicts the annotation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false).

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?

Usage triggers are front-loaded before the mechanical input tips, which is the right ordering. It is a fairly dense paragraph that packs usage, input rules, an inline example, optional fields, returns, exclusions and errors; the inline example partially duplicates the schema's own example, a minor redundancy, but no sentence is filler.

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 an output schema already present, the description need not explain return values yet still summarizes them, and it covers the remaining gaps an agent would face: input cardinality, required timezone, recurrence shape, and error semantics. For a file-generation tool with 2 params this is complete.

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 description coverage is 100%, so the baseline is 3 and the schema already documents each field. The description still adds value by restating the accepted date/time forms, the 1-50 event bound, and the critical timezone rule ('ask the user for the time zone, never guess it') plus a worked event example, though most of the per-field detail duplicates 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?

The description opens with a precise verb+resource ('make a calendar file' / .ics) and immediately grounds it in recognizable user phrasings. It is unambiguous against siblings like make_csv_file because the artifact type and use case (import into a calendar) are named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states exactly when to use it with three concrete trigger phrases, and it explicitly carves out the negative case: 'Not for: adding, changing or reading events in Google Calendar, Outlook or any calendar account; it only makes a file.' That is an explicit when/when-not with the nearest alternative behavior excluded.

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

All Document Tools 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.