Skip to main content
Glama

Coline

Update calendar

update_calendar
Idempotent

Renames or recolors a calendar, or changes how it shows for the person (hidden, counted for availability, where new events go).

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": {
      "workspace": "<workspace>",
      "calendarId": "<calendarId>"
    },
    "name": "update_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendarNoThe calendar itself, for everyone; needs manage permission.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
calendarIdYesCalendar id from list_calendars.
preferencesNoHow it shows for the person only.

Output Schema

NameRequiredDescriptionDefault
updatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds the useful scope distinction that some fields are calendar-wide and some are personal-only, but it omits permission requirements (the schema notes 'needs manage permission') and any note about partial updates or what is left untouched.

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?

One sentence, front-loaded with the changeable aspects, with the user-facing scope qualifier set off in parentheses. No filler, no restatement of the title.

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?

An output schema exists and the input schema is fully described, so return values and parameter meanings do not need to be repeated. However, for a mutation tool sitting beside four similarly named update_calendar* siblings, the description does not establish which sibling handles calendar-wide settings versus calendar sets, leaving a real ambiguity unaddressed.

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 100% with nested object descriptions, so the baseline is 3; the description earns an extra point by translating the opaque preference fields into plain language: 'hidden' maps to isVisible, 'counted for availability' to includeInAvailability, and 'where new events go' to isDefaultDestination. It does not mention colorOverride, sortPosition, timeZone, or defaultReminderMinutes, but the schema does.

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?

The description gives a specific verb set (renames, recolors, changes display) against a specific resource (a calendar), and separates calendar-wide changes from per-person display changes. It never names a sibling such as update_calendar_settings or update_calendar_set, so the agent gets a clear purpose but no explicit differentiation.

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?

Usage is only implied by the parenthetical field list (hidden, availability, default destination); there is no statement of when to use this instead of update_calendar_settings, update_calendar_set, or share_calendar, and no prerequisites are stated in the description text. Adequate but leaves routing to inference.

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.

Resources