Skip to main content
Glama

Coline

Create calendar set

create_calendar_set

Makes a named group of calendars the person can show together, optionally switched on automatically at set hours.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNo
autoRuleNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
calendarIdsYes

Output Schema

NameRequiredDescriptionDefault
setYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that the auto-show rule is optional and time-based — but says nothing about permissions, whether duplicate names are rejected, or the 100-calendar cap.

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 'at set hours' is slightly vague where a few more words about the schedule window would have earned their place.

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

Completeness4/5

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

place

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 20%, so the description must compensate. It does convey meaning for three of the five parameters in prose (name via 'named', calendarIds via 'group of calendars', autoRule via 'switched on automatically at set hours'), but color and the minute/timeZone semantics are left entirely to the schema, whose nested autoRule details are described only for the 'days' field.

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 concrete verb-and-resource statement ('Makes a named group of calendars') and explains the resulting object, so an agent can tell this apart from create_calendar (a single calendar). It does not name any sibling explicitly, so it falls just short of a 5.

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: the phrase 'optionally switched on automatically at set hours' hints that autoRule is optional, but there is no statement of when to choose this over update_calendar_set or create_calendar, and no prerequisites (permissions, workspace context) are given.

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