Skip to main content
Glama
dipseth

google-workspace-unlimited

Create New Calendar

create_calendar

Create a new Google Calendar with a required name and optional details like description, timezone, and location.

Instructions

Creates a new Google Calendar with specified properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesThe name/title of the calendar
locationNoGeographic location of the calendar (e.g., 'New York, NY', 'Conference Room A')
time_zoneNoTimezone for the calendar (e.g., 'America/New_York', 'Europe/London', 'UTC'). If not specified, uses the user's default timezone
descriptionNoOptional description of the calendar's purpose
user_google_emailNoThe user's Google email address for Calendar access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
messageYes
successYes
summaryYes
htmlLinkYes
locationYes
timeZoneYes
userEmailYes
calendarIdYes
descriptionYes
Behavior2/5

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

Annotations indicate readOnlyHint=false, but description does not add behavioral context like required permissions, side effects, or that it creates a new calendar resource in the user's account.

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 sentence with no unnecessary words. Front-loaded with action and resource.

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?

Adequate but could include more context such as that the calendar is created in the user's primary account unless user_google_email is specified, or that create_event is used to add events.

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 description coverage is 100%, so baseline is 3. Description does not add meaning beyond the schema's parameter descriptions.

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 action (creates) and the resource (new Google Calendar), with the specific properties. It distinguishes from sibling tools like create_event or list_calendars.

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 versus alternatives such as bulk_calendar_operations. Does not mention prerequisites or exclusions.

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/dipseth/google_workspace_fastmcp2'

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