Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Update calendar

update_calendar

Rename or recolor an existing calendar by its current name or URL. Use it to change a calendar's name or color, not its events.

Instructions

Renames or recolors one of the user’s calendars — the calendar itself, not an event on it. Use this when the user wants to rename a calendar or change its color; name the calendar by its current name or its URL from list_calendars. Returns the changes made and the calendar’s URL; when no calendar matches, the error lists every calendar with its URL, and nothing is changed. To change an event, use update_calendar_event; to add a new calendar, use create_calendar. Safe to re-run.

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": {
      "calendar": "<calendar>"
    },
    "name": "update_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name; must differ from every other calendar’s name. Omit to keep the current name.
colorNoNew color as a hex value, e.g. "#2E6FD8". Omit to keep the current color.
calendarYesThe calendar to change: its current name (matched ignoring case) or its URL, both as list_calendars shows them. Use the URL when two calendars share a name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: atomic failure ("when no calendar matches... nothing is changed"), the error payload enumerating all calendars with URLs, the return value (changes made plus the calendar's URL), and retry safety. Annotations already declare non-read-only, non-destructive, non-open-world, so the added atomicity and error-shape detail is the valuable part; "Safe to re-run" sits in mild tension with idempotentHint=false, but it describes retry safety rather than guaranteeing identical responses, so it is not a hard contradiction.

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?

Front-loaded with purpose, then identification, then return/error behavior, then alternatives and safety — every clause carries unique information. It is a dense single paragraph with stacked em-dash clauses, slightly harder to scan than a bulleted or two-paragraph form, but there is no filler.

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?

For a three-parameter mutation tool with no output schema and no annotation coverage of return values, the description supplies what is missing: what comes back, what happens on a failed match, and how to recover (the error lists every calendar with its URL). Nothing an agent needs to call it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds operative meaning: the calendar argument accepts either the current name or the URL as list_calendars presents it, and the URL is the disambiguator when two calendars share a name. That routing-to-list_calendars guidance is not merely a restatement of the schema.

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?

"Renames or recolors one of the user's calendars — the calendar itself, not an event on it" gives a specific verb pair, the exact resource, and an explicit disambiguation from the event-level sibling. An agent can distinguish this from update_calendar_event or create_calendar without opening any schema.

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?

States the triggering intent ("when the user wants to rename a calendar or change its color"), how to identify the target (current name or URL from list_calendars), and names the two alternatives for adjacent intents (update_calendar_event, create_calendar). Both when-to-use and when-not-to-use are covered.

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