Skip to main content
Glama

Coline

Update calendar set

update_calendar_set
Idempotent

Renames a calendar set or changes which calendars are in it.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNo
setIdYesCalendar set id from list_calendar_sets.
autoRuleNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
calendarIdsNo
sortPositionNo

Output Schema

NameRequiredDescriptionDefault
setYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare non-readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. Beyond that, the description adds nothing: it does not say whether calendarIds replaces or appends to the existing set, whether omitted fields are preserved, or what happens to sortPosition/autoRule.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity comes at the cost of coverage rather than being tight-but-complete.

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?

A 7-parameter mutation tool with low schema description coverage deserves more than one sentence. An output schema exists so return values need not be explained, but the update semantics (partial vs full update) and the four undocumented parameters are real gaps.

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?

Schema coverage is only 29%, so the description must compensate, and it does not. It accounts for name and calendarIds but gives no semantics for color, autoRule, or sortPosition, and critically leaves the replace-vs-merge behavior of calendarIds unexplained.

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 (renames/changes membership) and resource (calendar set), which distinguishes it from update_calendar (a single calendar) and settings tools. However, it presents the tool as narrower than it is, omitting color, autoRule, and sortPosition changes.

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?

No indication of when to use this versus update_calendar, update_calendar_settings, or create/delete_calendar_set. The sibling set is crowded with calendar-mutating tools, and the description offers no routing guidance.

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