Skip to main content
Glama
Sign In
mcp-calendar-python

mcp-calendar-python

by tobedoit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_event

Create a calendar event with title, time, location, attendees, and optional Google Meet link.

Instructions

Create a calendar event with specified details

Args: summary: Event title start_time: Start time (ISO format) end_time: End time (ISO format) description: Event description location: Event location attendees: List of attendee emails reminders: Reminder settings for the event calendar_id: Calendar ID (default: 'primary') timezone_str: Timezone ID (default: Asia/Seoul) create_meet_link: If True, enable Google Meet link

Returns: String with event creation confirmation and link

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "summary": "<summary>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYes
start_timeYes
end_timeYes
descriptionNo
locationNo
attendeesNo
remindersNo
calendar_idNoprimary
timezone_strNoAsia/Seoul
create_meet_linkNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so description must disclose behavior. It states creation and return of a confirmation string with link, but lacks side-effect details, permissions, or constraints (e.g., conflict handling, rate limits).

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?

Well-organized with 'Args' and 'Returns' sections, each parameter on its own line. No fluff, but the list is long (10 items) which is acceptable for the parameter count.

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?

Covers purpose, parameter explanations, and return value adequately. However, lacks behavioral details like whether it can create events in the past, recurrence support, or attendee limits. With an output schema present, return format detail is unnecessary.

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?

With 0% schema coverage, the description adds significant meaning: specifies ISO format for times, explains each parameter's purpose (e.g., 'List of attendee emails'), and mentions default values and the effect of create_meet_link. However, 'reminders' remains vague (opaque object).

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?

Clear verb 'Create' and resource 'calendar event' with specific details. The description distinguishes from the only sibling tool 'health' which is unrelated.

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 or not use this tool. No alternatives or exclusions provided, leaving the agent without usage context.

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

Deploy Server

Other Tools