Skip to main content
Glama

Update personal calendar event

bb_update_calendar_event
Idempotent

Update a personal calendar event you created by changing its title, dates, location, or description. Use the event ID from the calendar list and confirm the change.

Instructions

Update an event you created (personal calendar only). Requires BB_ALLOW_WRITES=1 and confirm:true.

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": {
      "itemId": "<itemId>"
    },
    "name": "bb_update_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
itemIdYesitem id from bb_list_calendar where userCreated=true
confirmNo
endDateNo
locationNo
startDateNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and idempotentHint=true, so the mutation/idempotency profile is covered structurally. The description adds real value beyond that by disclosing the BB_ALLOW_WRITES=1 environment gate and the confirm:true requirement. However it says nothing about partial-update semantics (which fields are untouched when omitted) or what happens when the event is not user-created.

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, no filler, with the scope restriction front-loaded before the operational prerequisites. Every clause carries information an agent needs before calling.

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 7-parameter mutation with no output schema and thin schema coverage, the description covers the critical gating (write flag, confirm) and ownership scope. It leaves gaps on partial-update semantics and date parameter formats, which matter given five undocumented optional fields.

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 only 14%, with itemId the sole documented parameter, so the description needs to compensate. It clarifies confirm:true as a required safeguard and reinforces itemId's personal-calendar provenance, but title, startDate, endDate, location, and description remain unexplained beyond self-evident names, and date formats are unstated.

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?

States a specific verb+resource ("Update an event") and narrows scope to "personal calendar only" plus ownership via "an event you created", which separates it from bb_create_calendar_event and bb_delete_calendar_event. It stops short of naming a sibling alternative, so it is clear but not fully differentiated.

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?

Gives a concrete precondition for use (event must be one you created, personal calendar only) and states the confirm:true gating requirement. It does not say when to prefer this over sibling mutation tools or what to do when the event is not user-created, so no explicit exclusion routing.

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