Skip to main content
Glama

Coline

Create calendar

create_calendar

Creates a calendar in the workspace: one of the person's own, or a shared one the team can see.

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": {
      "workspace": "<workspace>",
      "kind": "<kind>",
      "name": "<name>",
      "timeZone": "<timeZone>"
    },
    "name": "create_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesuser: the person's own; shared: the team's.
nameYes
colorNo
timeZoneYesIANA time zone, e.g. America/Vancouver.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo

Output Schema

NameRequiredDescriptionDefault
calendarIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds that creation is workspace-scoped and can target a personal or team-visible calendar, but says nothing about side effects (auto-subscription, default color), retry behavior given non-idempotency, or required permissions.

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?

A single front-loaded sentence with no filler, and the user/shared distinction is placed where it is most useful. It is efficient but borders on under-specified rather than tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a straightforward create mutation: 6 flat parameters, no nesting, annotations covering the safety profile, and an output schema so return values need not be described. Given that richness, the description covers what an agent needs to select and call it, with the unresolved gap being sibling disambiguation rather than missing context.

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 only 50%, and the three documented parameters (kind, timeZone, workspace) already carry their own explanations in the schema, so the description adds essentially nothing new. The undocumented fields — name, color, and description — receive no explanation of defaults, constraints, or effects from the description either.

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?

States a specific verb and resource ("Creates a calendar") and scopes it to the workspace, plus distinguishes the two flavors it can produce (personal vs. shared). It does not differentiate itself from the similarly named sibling create_calendar_set, so an agent could still hesitate between the two.

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?

There is no when-to-use guidance: no prerequisites (workspace slug required), no limits (quota, duplicate names), and no mention of alternatives such as create_calendar_set for calendar collections or share_calendar for granting access. The only implicit guidance is the user/shared distinction, which is really parameter semantics.

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.

Resources