Skip to main content
Glama

Coline

Update event

update_event
DestructiveIdempotent

Reschedules, renames, changes attendees of, or cancels an event. Only the fields you pass change. For a repeating event, say which occurrences change.

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": {
      "workspace": "<workspace>",
      "eventId": "<eventId>"
    },
    "name": "update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoISO 8601 with a time zone offset, e.g. 2026-11-20T15:00:00-08:00.
kindNo
colorNo
linksNoFiles, channels or web pages to attach.
startNoISO 8601 with a time zone offset, e.g. 2026-11-20T15:00:00-08:00.
titleNo
allDayNo
cancelNotrue cancels the event for everyone.
eventIdYesEvent id from list_events.
locationNo
timeZoneNoIANA time zone, e.g. America/Vancouver.
attendeesNoEmail addresses. Teammates are added directly; anyone else gets an email invite once the person approves it.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
calendarIdNoCalendar to put it on; default the person's own.
visibilityNo
callJoinUrlNoA video call link from elsewhere.
descriptionNo
callProviderNo
transparencyNofree: doesn't block the person's time.
guestAttendeesNoPeople outside Coline, with a name and time zone.
recurrenceRuleNoHow it repeats; {} or null stops it repeating.
attendeeUserIdsNoTeammates by user id, instead of attendees by email.
meetingSettingsNo
occurrenceStartNoWhich occurrence, by its start, with recurrenceScope this or following.
recurrenceScopeNoFor a repeating event: this occurrence, this and following, or the whole series.
travelMinutesAfterNo
travelMinutesBeforeNo

Output Schema

NameRequiredDescriptionDefault
eventYes
invitesYesWhether emails to people outside Coline went out, or wait for the person's approval in Coline.
approvalUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the safety profile is covered; the description adds real value beyond that by stating the patch semantics (unpassed fields are left alone) and the requirement to scope recurrence. It stops short of disclosing whether cancellation is reversible or what notifications it triggers.

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?

Three short sentences, front-loaded with the mutation verbs and followed by the two most consequential constraints. Every sentence earns its place, though the recurrence sentence could be slightly more explicit about the parameter that carries it.

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?

An output schema exists so return values need no explanation, and the description covers the two behaviors an agent would most likely get wrong: overwriting fields and applying a change to an entire series. What remains missing is the destructive-cancel consequence, which is material for a tool rated 27 parameters wide.

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?

With 27 parameters and only 59% schema description coverage, the description should carry more weight. It does add meaning for the recurrence pair by saying "say which occurrences change," but leaves large groups such as meetingSettings, visibility, links, and travel time entirely to 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?

The description names specific verbs (reschedules, renames, changes attendees, cancels) against a specific resource (an event), so the agent can immediately tell this apart from siblings like create_event, delete_event, or attach_to_event.

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

Usage Guidelines3/5

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

"Only the fields you pass change" establishes partial-update semantics, and the repeating-event sentence tells the agent when recurrence scoping matters. However, no guidance distinguishes cancelling here from the sibling delete_event, and there is no statement about prerequisites or preconditions for the update.

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