Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Create calendar

create_calendar

Creates a new calendar for the authenticated user, with an optional color, to keep a workstream's events separate and returns its CalDAV URL for adding events.

Instructions

Creates a new calendar for the authenticated user, with an optional color. Use this when the user wants to keep a workstream’s events separate from their other calendars. Returns the new calendar’s CalDAV URL; pass it to create_calendar_event to add events to it. Each call makes another calendar, so check list_calendars first; to rename or recolor an existing calendar use update_calendar instead.

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": "create_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that each call creates another calendar (reinforcing non-idempotency), that the return value is a CalDAV URL, and that this URL must be passed to create_calendar_event. That is meaningful behavioral context an agent could not infer from the structured fields alone.

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 three dense sentences with no filler: purpose first, usage guidance second, and behavioral cautions/return-value routing last. Every clause contributes to correct selection or invocation.

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

Completeness4/5

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

For a non-destructive but non-idempotent creation tool with no output schema, the description covers return value, duplicate avoidance, and the sibling alternative well. The main gap is that parameter constraints are left entirely to the schema despite 0% schema description coverage.

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%, so the description should carry parameter meaning, but it only says the color is optional. It does not explain the required name's role or constraints, nor does it mention the hex color pattern enforced by the schema. The schema itself is the only source of those details.

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 uses a specific verb and resource: 'Creates a new calendar for the authenticated user.' It also distinguishes this from update_calendar and list_calendars by naming them explicitly, so an agent can immediately tell what this tool does and does not do.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ('when the user wants to keep a workstream’s events separate'), a prerequisite ('check list_calendars first'), and a named alternative for a different operation ('to rename or recolor an existing calendar use update_calendar instead').

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