Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calendar_event_create

Create Google Calendar events with start/end times, attendees, location, description, and optional Google Meet links; date-only inputs create all-day events.

Instructions

Create an event. start/end are RFC3339 datetimes; date-only ('2026-06-10') makes an all-day 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": {
      "account": "<account>",
      "summary": "<summary>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "calendar_event_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
accountYes
summaryYes
locationNo
timezoneNo
attendeesNo
calendar_idNoprimary
descriptionNo
send_updatesNonone
add_google_meetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description explains the start/end format nuance but omits other behavioral aspects like permissions, error conditions, side effects of attendee list or send_updates, and return value structure.

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 extremely concise: two sentences that convey the essential action and a critical formatting note. Every word adds value.

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?

Given the complexity of 11 parameters, no output schema, and no annotations, the description is incomplete. It covers the datetime nuance but nothing about return values, error handling, or timezone behavior.

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%, yet the description only adds meaning for two parameters (start, end) out of eleven. The remaining parameters (account, summary, calendar_id, etc.) are left entirely to schema property names.

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 the tool's purpose: 'Create an event.' It also adds a useful detail about datetime format and all-day event creation, which is specific and helpful.

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?

The description does not provide any guidance on when to use this tool versus alternatives (e.g., calendar_event_update), nor does it mention prerequisites or conditions for use.

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