killbottleneck-mcp

Official

Overview Schema Source Related Servers Discussions Admin

update_event

Modify an existing calendar event by ID, including personal events, shared calendar events as admin or manager, and time off. Update only specified fields; empty strings clear values.

Instructions

Change an existing event by id: your own, one in a shared calendar as admin/manager, or your own time off. Only the given fields change; an empty string clears time, end_day, end_time or calendar (calendar "" = make it personal). Moving day of a multi-day event keeps its length. participants replaces the whole list; remind false cancels the reminder.

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": "update_event"
  }
}

Input Schema

Name	Required	Description
`day`	No	YYYY-MM-DD
`note`	No
`time`	No	HH:MM (24h); "" = all day
`place`	No	where it takes place; "" = clear
`title`	No
`remind`	No	false cancels the reminder
`end_day`	No	YYYY-MM-DD; "" = single day
`calendar`	No	name or id of a shared calendar; "" = personal
`end_time`	No	HH:MM (24h); "" = no end time
`event_id`	Yes
`participants`	No	the complete new list of member e-mails
`remind_before_min`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.1Nov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses partial-update semantics, empty-string clearing behavior, calendar reassignment semantics, multi-day event duration preservation, full replacement of participants, and reminder cancellation via remind=false. It does not describe permission failures or return behavior, but the key mutation semantics are transparent.

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?

The description is front-loaded and dense with useful semantics, with every sentence contributing operational guidance. It avoids repetition and keeps the mutation rules easy to scan.

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 12-parameter mutation tool with no annotations and no output schema, the description covers the core update behaviors, ownership constraints, and clearing/replacement rules. It leaves some secondary parameters and failure-response behavior unaddressed, but it is substantially complete for correct invocation.

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 coverage is 67%, and the description adds important meaning beyond the schema for tricky parameters such as time, place, end_day, end_time, calendar, participants, and remind. It does not add detail for note, title, or remind_before_min, but it compensates for the most consequential ambiguities.

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 states a specific verb and resource, 'Change an existing event by id,' and immediately clarifies the permitted ownership/admin scopes. It distinguishes this mutation from create/delete siblings by focusing on changing existing events and describing which events can be changed.

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 clearly explains when this tool applies, including your own events, shared-calendar events as admin/manager, and your own time off. It does not explicitly name create_event or delete_event as alternatives, but the usage context is still clear for an agent.

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