Hopi

Add to calendar file generator

hopi_ics_generator

Read-onlyIdempotent

Build a .ics (iCalendar, RFC 5545) calendar file for a single event and return the file text. Give a title, startDate and endDate as 'YYYY-MM-DD'. For timed events give startTime and endTime as 'HH:MM' (24-hour, read in the caller's local time zone and stored as UTC); set allDay true for an all-day event instead. Location and description are optional. Returns the .ics text ready to save. Source: https://hopi.co.uk/ics-generator/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	Yes	Event title (SUMMARY)
`allDay`	No	True for an all-day event (no times). Default false
`endDate`	No	End date, ISO 'YYYY-MM-DD'. Defaults to startDate
`endTime`	No	End time 'HH:MM' 24-hour, timed events only. Defaults to startTime
`location`	No	Optional location
`startDate`	Yes	Start date, ISO 'YYYY-MM-DD'
`startTime`	No	Start time 'HH:MM' 24-hour, timed events only. Default '00:00'	00:00
`description`	No	Optional description

Output Schema

TableJSON Schema

Name	Required	Description
`ics`	Yes
`bytes`	Yes
`title`	Yes
`allDay`	Yes
`summary`	Yes
`filename`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedOutput schema / required

Added value: +[
+  "allDay",
+  "bytes",
+  "filename",
+  "ics",
+  "source_url",
+  "summary",
+  "title"
+]

First observedSep 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this tool as read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond that: times are interpreted in the caller's local timezone and stored as UTC, allDay changes the event structure, and the result is text ready to save. No contradiction with annotations.

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?

The description is compact and front-loaded: it states the core purpose in the first sentence, then packs essential format and option guidance into a few sentences. The source link is a reasonable addition and does not feel like 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?

The description covers all 8 parameters, explains required formats, optionality, and the timed-vs-all-day distinction. Since an output schema is present, the return format need not be further elaborated. An agent has enough to call this tool correctly.

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 schema already documents all parameter meanings and defaults. The description adds useful semantics not in the schema, such as the local-timezone-to-UTC conversion and the relationship between startTime/endTime and allDay.

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 ('Build') and resource ('a .ics calendar file for a single event') and explicitly says it returns the file text. This clearly distinguishes it from the many unrelated hopi_* calculator/converters in the sibling list.

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 usage context: how to supply dates, how to distinguish timed events from all-day events via allDay, and which fields are optional. It does not explicitly name excluded alternatives, but no closely related sibling exists, so this is not a significant gap.

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

All Hopi 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.

Resources

Need Help?