Skip to main content
Glama

calendar update event

calendar_update_event
Idempotent

Modify an existing calendar event by patching selected fields such as summary, times, location, attendees, and description, so targeted changes can be made without recreating the event.

Instructions

Patch fields on an existing event (summary, times, location, attendees).

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": {
      "event_id": "<event_id>"
    },
    "name": "calendar_update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
summaryNo
event_idYes
locationNo
attendeesNo
time_zoneNo
calendar_idNoprimary
descriptionNo
send_updatesNonone

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral signal — 'Patch' implies partial/null-safe updates rather than full replacement — but it never mentions send_updates notification behavior, which materially affects attendees when patching an event.

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; the parenthetical list is compact and readable. It could have spent the same words on the higher-risk undocumented parameters instead.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, for a 10-parameter mutation with zero schema descriptions and attendee-notification side effects, the description leaves too much of the calling contract implicit.

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% across 10 parameters, so the description carries the full burden, yet it only touches summary, start/end, location and attendees. It says nothing about calendar_id, time_zone, description, or send_updates, and gives no format hints for the string time values.

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?

The description pairs a specific verb ('Patch fields') with a specific resource ('an existing event') and enumerates the patchable fields. 'Existing event' implicitly separates it from calendar_create_event and calendar_delete_event without naming them.

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 mention of prerequisites such as needing a resolvable event_id or the default 'primary' calendar, and no routing to siblings like calendar_create_event for new events or calendar_get_event for reads. The agent must infer invocation context entirely.

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