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

python-mcp-server

by Potato-29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

createEvent

Create Google Calendar events by specifying a title, start and end times, and optional attendees, description, or full-day setting.

Instructions

Create a new Google Calendar event

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>",
      "startDateTime": "<startDateTime>",
      "endDateTime": "<endDateTime>"
    },
    "name": "createEvent"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYesThe title/summary of the event
attendeesNoList of attendee email addresses
isFulldayNoIs the event a full day event
descriptionNoOptional description for the event
endDateTimeYesEnd date and time in ISO format (e.g., '2025-07-10T14:30:00Z')
startDateTimeYesStart date and time in ISO format (e.g., '2025-07-10T12:30:00Z')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations provided. Description lacks any behavioral disclosure such as authentication requirements, rate limits, side effects, or success/failure behavior for a creation tool.

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?

Single sentence with no waste. It is front-loaded with the action. Could include more context but remains appropriately concise for a simple tool.

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, yet the description does not mention return values, event confirmation, or any post-creation behavior. Incomplete for a creation tool with 6 parameters and no annotations.

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

Parameters3/5

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

Schema coverage is 100%, with all 6 parameters described in the input schema. However, the description adds no extra meaning beyond what the schema provides, staying at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Create a new Google Calendar event', which is a specific verb+resource combination. It distinguishes from the sibling 'add-note' tool, though not explicitly.

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 mention of prerequisites, restrictions, or comparisons with alternatives like 'add-note'.

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