Skip to main content
Glama

Update calendar event

event_update
Idempotent

Update a calendar event by ID. Fields omitted are unchanged. Changes to a published event wait as a draft until the person approves publishing (confirm_publish: true). Setting status published needs the person's approval and confirm_publish: true. Requires API key scope: draft.

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": {
      "id": "<id>",
      "updates": "<updates>"
    },
    "name": "event_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
updatesYes
confirm_publishNotrue only after the person explicitly approved publishing; required whenever this call publishes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare the safety profile (mutation, idempotent, non-destructive, not open-world). The description adds behavior the annotations cannot convey: partial-update semantics (omitted fields unchanged), that edits to a published event are staged as a draft pending human approval, and the required API key scope "draft".

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 operation and partial-update rule, then the publishing caveats, then the scope requirement. The two adjacent sentences about approval/confirm_publish cover subtly different cases (editing a published event vs. publishing) but read somewhat repetitively.

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 mutation tool with a nested payload, no output schema, and low schema coverage, the description covers the traps an agent could fall into: partial updates, draft staging, approval gating, and auth scope. Return shape and any side effects (notifications, etc.) are left unstated, which is the main remaining gap.

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 description coverage is only 33% and the nested updates object has a dozen undocumented properties. The description compensates for the most consequential gaps by explaining that omitted fields are left unchanged and by spelling out the confirm_publish approval gate, though it adds nothing about individual field meanings like starts_at/timezone.

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?

"Update a calendar event by ID" gives a specific verb and resource, and the sibling set (event_create, event_cancel, event_list) makes the update-vs-create-vs-cancel boundary obvious. It stops short of explicitly naming an alternative, but the operation is unmistakable.

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

Usage Guidelines4/5

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

It states the conditions under which confirm_publish is needed (publishing, or approving changes to an already-published event), which is the real decision point for this tool. It does not explicitly exclude nearby cases (e.g., "to cancel an event use event_cancel"), so it is clear context rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources