Skip to main content
Glama

Set calendar pause

set_calendar_pause
Destructive

In ONE call, switch chosen series of a project's calendar off for a period — kind 'pause', e.g. every class of the week of run-throughs: name the events by 'events' (eventIds), 'externalIds' or a 'label' they carry — or mark DAYS OFF — kind 'dayoff', a holiday: no occurrence of any repeating event lands on it. Only the days 'from'..'to' (inclusive, at most 366) are touched; other weeks are not. Nothing is rewritten: lifting it with delete_calendar_pause brings the occurrences back, except one somebody changed by hand after the pause began, which keeps that change. Answers the pause and 'affected', how many occurrences it takes off. Anybody who may write in the project.

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": {
      "project": "<project>",
      "kind": "<kind>",
      "from": "<from>"
    },
    "name": "set_calendar_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoThe last day, YYYY-MM-DD; default the first.
fromYesThe first day, YYYY-MM-DD.
kindYes'pause' or 'dayoff'.
labelNoA pause takes every event with this label.
eventsNoA pause's events as eventIds, 'a,b'.
reasonNoWhy — 'run-through week', 'New Year'.
projectYesThe project key, e.g. TH.
externalIdsNoA pause's events by their external ids, 'a,b'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: scopes the effect to the inclusive from..to window with a 366-day cap, promises nothing is rewritten, and describes reversibility via delete_calendar_pause including the exception for occurrences edited by hand after the pause began. It also names the return payload ('the pause and affected, how many occurrences it takes off') and the authorization requirement ('Anybody who may write in the project').

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?

The operative instruction ('In ONE call, switch...') is front-loaded, and the modifier clauses are ordered as operation, selectors, scope, reversibility, response, permissions. The dash-heavy, sentence-long phrasing makes it denser than necessary, but no sentence is filler.

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

Completeness5/5

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

With 8 parameters, no output schema and no enums, the description covers the kind branching, selector semantics, date window and cap, return shape, reversibility semantics and permissions. Nothing an agent needs to invoke this destructive mutation correctly is missing.

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% so the baseline is 3, but the description adds real meaning: label/events/externalIds are selectors that apply only to the 'pause' kind, and from/to bound an inclusive window with a maximum span. It does not, however, add format or syntax beyond what the schema already says for those fields.

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

Purpose5/5

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

States a specific verb and resource ('switch chosen series of a project's calendar off', or mark days off) and enumerates the two kinds, 'pause' and 'dayoff', with the selector options (events, externalIds, label). It is clearly distinguishable from the inverse sibling delete_calendar_pause and from mutation siblings like set_calendar_event.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the choice between kinds with concrete framing ('every class of the week of run-throughs' vs 'a holiday: no occurrence of any repeating event lands on it') and points to delete_calendar_pause for lifting a pause. It stops short of stating when to use set_calendar_event or set_calendar_occurrence instead, so no explicit exclusion against the other write siblings.

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