Skip to main content
Glama

Coline

Update calendar settings

update_calendar_settings
Idempotent

Changes the person's calendar settings. Only the fields you pass change.

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>"
    },
    "name": "update_calendar_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeZoneNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
timeFormatNo
defaultViewNo
showWeekendsNo
weekStartDayNo
bufferMinutesNo
reviewRitualTimeNo
planningRitualTimeNo
showDeclinedEventsNo
reviewRitualEnabledNo
defaultEventDurationNoMinutes.
planningRitualEnabledNo
defaultEventVisibilityNo
defaultReminderMinutesNo

Output Schema

NameRequiredDescriptionDefault
timeZoneYes
timeFormatYes
defaultViewYes
weekStartDayYes
defaultEventDurationYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/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 structurally. The description does add one genuinely useful behavioral fact beyond annotations: partial/patch semantics, where only fields supplied are modified. It says nothing about what is returned, whether unknown fields error out, or whether changes are visible to other workspace members.

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 short sentences, front-loaded with the action and immediately followed by the patch-semantics qualifier — no filler or repetition. It is arguably too terse for a 15-parameter tool, but nothing present is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a 15-parameter mutation tool with 13% schema coverage, one described required parameter, and four enum-bearing fields, two sentences are far from sufficient. An agent could not reliably map intent to the correct parameter names or units without opening the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 15 parameters and only 13% schema description coverage, the description carries a heavy burden and meets almost none of it. It never mentions the setting groups available (time zone, time format, week start, buffers, ritual toggles/times, default event duration/visibility/reminder) or units such as bufferMinutes and reviewRitualTime, which are bare integers in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb and resource are named ("Changes the person's calendar settings"), so an agent knows this is a mutation of calendar settings. However it does not say which settings are covered or how it differs from the many similarly-named siblings such as update_calendar, update_calendar_set, update_settings, and get_calendar_settings, all of which sound like the same resource.

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 when-to-use guidance, no exclusion of alternatives, and no mention of prerequisites (e.g., you must already know the workspace slug, and read current values via get_calendar_settings first). The only implicit guidance is that unpassed fields are left alone.

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