Skip to main content
Glama
Sign In
Recued

Recued

by recued
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

calendar.update

Update an existing calendar event by moving, renaming, or cancelling it with the source_id from calendar.search; changes are proposed for confirmation before applying.

Instructions

Change an event already on the user's calendar — move it, rename it, or cancel it by setting status to cancelled. ⚠ This CHANGES a commitment other people may have seen, so it is proposed to them first and only runs once they confirm. ⛔ Find the event with calendar.search and use the source_id it returned. Never guess an id, and never update when the search returned more than one plausible match — say which ones you found and ask which they mean. Sending the wrong id edits somebody else's meeting. ⚠ Send ONLY the fields that change; anything you omit keeps its current value. Do not restate the whole event, and do not re-send a field you did not mean to touch.

Input Schema

NameRequiredDescriptionDefault
end_atNoOptional new end, Unix ms.
statusNoOptional — set 'cancelled' to call the event off. Outlook keeps no cancelled events, so there it deletes the event.
summaryNoOptional new title. Omit to leave it alone.
start_atNoOptional new start, Unix ms. Send `end_at` too when moving an event, or it keeps its old end.
timezoneNoOptional IANA zone for the new times. Required when you send a new `start_at` in a different zone.
source_idYesREQUIRED — the id of the event to change, exactly as `calendar.search` returned it.
calendar_idNoOptional — the calendar connection the event is on: the `collection_slug` calendar.search returned for it, not its `calendar_id`. Omit for the local calendar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv26.11.3
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Optional — the calendar instance the event lives on. Omit for the local calendar."New value: +"Optional — the calendar connection the event is on: the `collection_slug` calendar.search returned for it, not its `calendar_id`. Omit for the local calendar."
    • changedInput schema / properties / status / description
      Previous value: -"Optional — set 'cancelled' to call the event off without deleting the record."New value: +"Optional — set 'cancelled' to call the event off. Outlook keeps no cancelled events, so there it deletes the event."
  2. First observedv26.10.22

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses that the change is proposed to affected people and only executes after their confirmation, that omitted fields retain their current value, and that cancellation is expressed through status. It stops short of stating permission requirements, attendee notification behavior, or reversibility of an applied edit.

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 the core action, then ordered risk warnings, then parameter discipline. Every sentence carries a distinct constraint; the warning glyphs cost little. Slightly verbose in the repetition of the 'do not send what you did not mean to touch' idea twice.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the highest-risk behaviors: identity resolution, the confirmation gate, and partial-update semantics. It leaves the response shape and failure modes (e.g., unknown source_id, permission denied) for the agent to discover.

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 baseline is 3, but the description adds cross-field meaning the schema only states piecemeal: send only the fields that change, everything omitted keeps its current value, and do not re-send untouched fields. The calendar_id vs source_id distinction and the 'cancelled' semantics remain primarily schema-borne.

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 first clause names a specific verb and resource ('Change an event already on the user's calendar') and enumerates the supported operations — move, rename, cancel via status. It is immediately distinguishable from calendar.create (creation) and calendar.search (lookup), which are named or implied.

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 sequencing (find the event with calendar.search first, use the returned source_id), an explicit prohibition (never guess an id), and a decision rule for the ambiguous case (if search returned more than one plausible match, report them and ask rather than updating). This is close to a complete when/when-not ruleset.

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

Deploy Server

Other Tools