Skip to main content
Glama

dialogbrain

by com.dialogbrain
OverviewDiscussionsAdmin

calendar_update_event

Update an existing event in Google Calendar. Can modify title, time, location, description, and attendees, and add a Google Meet link to an event that has none. Only specified fields will be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoNew end time in ISO 8601 format. Optional.
startNoNew start time in ISO 8601 format. Optional.
summaryNoNew event title/summary. Optional.
event_idYesID of the event to update. Required.
locationNoNew event location. Optional.
attendeesNoNew list of attendee emails. Replaces existing attendees.
calendar_idNoCalendar ID containing the event. OMIT to use the agent's configured default calendar (or primary).
descriptionNoNew event description. Optional.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
add_google_meetNoIf true, gives the event a Google Meet link of its own when it has none; an event that already has one keeps it. OMIT to leave the event's link as it is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / add_google_meet
      Added value: +{
+  "description": "If true, gives the event a Google Meet link of its own when it has none; an event that already has one keeps it. OMIT to leave the event's link as it is.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true. The description adds partial-update semantics ('only specified fields will be updated'), which is useful, but the Meet-link behavior it mentions is duplicated from the schema. No mention of permissions, attendee-notification side effects, or return behavior.

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 verb and resource, and the partial-update clause earns its place by clarifying patch behavior. No filler, though nothing is said about the required event_id.

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 10-parameter mutation tool with full schema coverage and safety annotations, the description covers scope, patch semantics, and the notable Meet-link case. It omits only permission/notification side effects and response behavior, which are relatively minor given the annotation coverage.

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 description coverage is 100%, so every parameter is already documented in the schema, including the ISO 8601 format, attendee replacement, calendar_id defaulting, and add_google_meet semantics. The description only restates the field list, adding no meaning beyond 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?

States a specific verb and resource ('Update an existing event in Google Calendar') and enumerates exactly what can be modified (title, time, location, description, attendees, Meet link). This clearly separates it from calendar_create_event, calendar_delete_event, and calendar_list_events.

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?

The phrase 'existing event' implies when to use it rather than create, and 'Only specified fields will be updated' signals patch semantics, but there is no explicit when-not guidance or named alternative tool. Usage is implied, not stated.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources