Skip to main content
Glama

create_calendar

Build an ICS calendar file by providing an array of events. Each event requires title, start, and end, with optional location, description, and all-day flag.

Instructions

Build a multi-event ICS calendar file from an array of events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendar_nameNoCalendar
eventsYes
Behavior2/5

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

No annotations provided. Description does not disclose what the tool returns (e.g., ICS file content as string), side effects, or output format. Minimal behavioral insight.

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?

Single, concise sentence with no redundancy. Efficiently conveys the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should clarify return type. Missing info on date formats, validation, or output handling. Incomplete for a tool generating a file.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds no parameter details beyond the schema structure (e.g., date format, optional fields). Misses opportunity to explain calendar_name default or event properties.

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 clearly states it builds a multi-event ICS calendar file from events, distinguishing it from sibling tools like create_event (single event) and parse_ics (parsing).

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., create_event for single event, google_calendar_url for web calendar). Missing prerequisites or context.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jeffereychown-Max/mcp-ical'

If you have feedback or need assistance with the MCP directory API, please join our Discord server