Skip to main content
Glama

Calendar: Update calendar

calendar_update_calendar
Destructive

Update explicit fields on an existing calendar. Resolve calendar_id first and pass only changes requested by the user.

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": {
      "calendar_id": "<calendar_id>"
    },
    "name": "calendar_update_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
timezoneNoIANA timezone, for example Europe/Paris.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
calendar_idYesExact calendar ID returned by calendar_list_calendars; never pass a calendar name. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.
descriptionNo
background_colorNoHexadecimal calendar color.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, destructive mutation, so the safety profile is covered. The description adds a useful partial-update signal ('explicit fields', 'only changes requested'), implying unspecified fields are left alone, but says nothing about what a failed update leaves behind, whether name collisions occur, or the account_id resolution path.

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?

Two tight sentences with the operation stated first and the precondition second; no filler. Slightly sparse rather than padded, but every clause earns its place.

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?

Adequate for a six-parameter mutation tool with no output schema, since annotations and schema do much of the work. It is still thin on partial-update semantics (are omitted fields preserved?) and on multi-account selection, both of which an agent must get right.

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 67% and the well-documented calendar_id and account_id already carry the lookup instructions. The description only reinforces 'resolve calendar_id first'; it adds nothing for the un-annotated name, description and background_color fields.

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 and resource ('Update explicit fields on an existing calendar'), which clearly separates it from calendar_create_calendar, calendar_delete_calendar and calendar_get_calendar. It stops short of naming a sibling explicitly, so it lands just below the top band.

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?

Gives two genuine usage rules: resolve calendar_id first and pass only the changes the user requested. It never states when to prefer calendar_update_event or calendar_create_calendar, nor what to do when a calendar_id cannot be resolved, so context is implied rather than explicit.

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.