Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__calendar_update_event

Destructive

Update an existing calendar event. Only provided fields are changed.

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": "gws-mcp__calendar_update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoNew end time (ISO 8601)
startNoNew start time (ISO 8601)
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
summaryNoNew event title
event_idYesThe calendar event ID to update
locationNoNew event location
attendeesNoComma-separated email addresses (replaces existing attendees)
calendar_idNoCalendar ID (default: "primary")
descriptionNoNew event description
send_updatesNoWho to send update notifications to (default: "all")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true. The description adds genuinely useful partial-update semantics ('Only provided fields are changed'), which tells the agent omitted fields are preserved. It omits important behavioral caveats, though: that 'attendees' REPLACES the existing attendee list (the most destructive aspect of this call), and that send_updates defaults to 'all', meaning notifications go out to everyone unless overridden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action, and the partial-update rule comes immediately after. Nothing is padded or redundant.

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?

For a 10-parameter mutation with a destructive hint and no output schema, the definition is adequate but thin. It should at minimum warn that attendees are overwritten wholesale and that notifications are sent by default, which directly affect whether an agent calls it safely.

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 each of the 10 parameters is already documented, including the comma-separated attendees format and the send_updates enum. The description reinforces the optional-parameter model but adds no field-specific meaning beyond what the schema states; baseline 3 is appropriate.

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?

Specific verb+resource: 'Update an existing calendar event.' An agent can distinguish it from calendar_create_event, calendar_delete_event, and calendar_get_event by name and description. It does not, however, explicitly name a sibling or scope (e.g., which fields or which calendars) beyond the second sentence.

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 explicit guidance on when to use this versus alternatives such as calendar_respond_to_event (RSVP) or calendar_suggest_time, nor any prerequisites (event must exist, ownership/attendee permissions). Usage is only implied by the word 'Update'.

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

All DataToRAG 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