Skip to main content
Glama

Calendar: Create calendar

calendar_create_calendar

Create a calendar in the selected Google or Microsoft account. Use only when the user explicitly asks for a new calendar, not merely an 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": {
      "name": "<name>"
    },
    "name": "calendar_create_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
timezoneNoIANA timezone, for example Europe/Paris.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
descriptionNo
background_colorNoHexadecimal calendar color.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, with openWorldHint=false, so the safety profile is covered. The description adds only the account-selection context; it says nothing about duplicate-name behavior, whether the new calendar is shared/visible to others, or whether a returned calendar is immediately usable for events.

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?

Two short sentences, purpose first and the disambiguation rule immediately after; nothing extraneous or hedged.

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?

For a mutating tool with no output schema, an agent still lacks guidance on what is returned (e.g., a new calendar ID), how to handle an existing calendar with the same name, and which permissions/scope are required. The core decision (create vs. create event) is fully covered, but mutation side effects are under-described.

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 60%, with account_id, timezone, and background_color already well documented in-schema; name and description parameters are undocumented. The description adds only a hint about account selection, which the schema already covers in depth, so baseline 3 is warranted.

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?

Specific verb+resource ("Create a calendar") plus scope ("in the selected Google or Microsoft account"), and it explicitly distinguishes itself from event creation, which is the main sibling confusion in this cluster.

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

Usage Guidelines4/5

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

Gives an explicit when-not rule ("not merely an event") that routes the agent to calendar_create_event, plus an implicit precondition that a provider account is selected. It doesn't name sibling tools like calendar_update_calendar or list_connected_accounts, but the exclusion is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.