Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Move calendar events

move_calendar_events

Move calendar events to another existing calendar without changing their time or content. Keeps uid, attendees, reminders and recurring series; attendees are not notified.

Instructions

Moves events from one of the user’s calendars to another — for example into a new "Private" calendar — without changing their time or content. Use this when the user wants events filed on a different calendar; to change when an event happens (“move the meeting to 3 pm”), use update_calendar_event instead. Events keep their uid, attendees, reminders and every occurrence of a recurring series, and attendees are not notified. Returns how many events moved and names each one that did not, with the reason; the destination calendar must already exist (create one with 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>",
      "uids": "<uids>"
    },
    "name": "move_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYesEvents to move, by the uid list_calendar_events shows. A recurring event moves as a whole series, including its changed occurrences. Up to 50 per call.
calendarYesDestination calendar: its name (matched ignoring case) or its URL, both as list_calendars shows them. It must already exist; calendars are never created here.
fromCalendarNoOnly needed when a uid exists in more than one calendar: the calendar to move it out of, by name or URL. Omit otherwise; each event is found wherever it is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that uid, attendees, reminders and the whole recurring series are preserved, that attendees are not notified, that the destination calendar is never auto-created, and what the response contains (count plus each failed event with a reason). One mild tension worth noting: 'Safe to re-run' sits alongside idempotentHint=false — a re-run would find the uids already gone and report failures, so 'safe' should be read as non-destructive rather than as a no-op guarantee, which a reader may conflate.

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?

Front-loads the action and scope, then the routing rule, then behavior, then return value — a deliberate and useful ordering. Every clause carries information an agent needs; the length is justified by substance rather than padding.

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 non-destructive mutation tool with no output schema, the description covers result shape (moved count, failed names plus reasons), preserved fields, side effects (no attendee notifications), and the creation precondition. An agent has everything needed to call it correctly and to interpret the outcome.

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 100%, so `uids`, `calendar` and `fromCalendar` are already fully documented in structured form, including the 50-event cap, name-or-URL matching, and the conditional use of `fromCalendar`. The description adds only marginal param-level meaning (recurring series move as a whole), so the baseline 3 is right.

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?

Opens with a specific verb and resource ('Moves events from one of the user's calendars to another') and states the scope constraint explicitly: time and content are unchanged. It also names the sibling it is not ('to change when an event happens ... use update_calendar_event instead'), so an agent can route between the two without opening either 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?

Gives an explicit when-to-use ('the user wants events filed on a different calendar'), an explicit when-not with the correct alternative named for the disambiguation trap ('move the meeting to 3 pm' → update_calendar_event), and the precondition that the destination must already exist (create one with create_calendar). Nothing about selection is left to inference.

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