Skip to main content
Glama

List calendar pauses

list_calendar_pauses
Read-only

A project's calendar PAUSES and DAYS OFF that end on 'since' or later: kind 'pause' (chosen series switched off for a period — 'events' it names and/or every event with 'label') or 'dayoff' (a holiday: no occurrence of a REPEATING event lands on it; an event that happens once stays). 'from'/'to' are days, inclusive, each read on the occurrence's own event's clock. The occurrences they take show in list_calendar_events with withCancelled as cancelled with 'pause'. Any member may read.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoYYYY-MM-DD; default yesterday.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world, and the description adds real semantic behavior: what 'pause' suppresses (a chosen series and/or every event with 'label'), that 'dayoff' blocks only repeating events while one-off events still occur, and that clocks are read per occurrence's own event. 'Any member may read' adds an access-permission note not in annotations. No return format or volume/pagination guidance, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every clause carries information, but it is delivered as one long run-on sentence with heavy parentheticals, uppercase emphasis, and a subject-less opening, so it is not front-loaded and requires re-reading. The kind definitions would be clearer as separate short statements.

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?

For a two-parameter read-only list with no output schema, the description supplies the domain semantics an agent needs (kinds, matching rules, per-event clocks, permission model). The notable gap is that it never describes what a returned pause/dayoff record contains, which matters since no output schema exists.

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 coverage is 100%, so the baseline is 3; the description clarifies that 'since' selects pauses whose end falls on or after that day, which adds meaning. However, it discusses 'from'/'to' days that do not exist in the schema (only 'project' and 'since' do), which muddies rather than clarifies parameter semantics.

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 the resource and scope precisely: a project's calendar pauses and days off that end on 'since' or later, split into kind 'pause' and 'dayoff'. It also distinguishes itself from list_calendar_events by explaining that paused occurrences surface there as cancelled. The opening is an elliptical noun phrase rather than a verb-led statement, so the verb has to be inferred from the name.

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?

Implies the reading use case (inspect pauses/daysoffs active since a date) and cross-references list_calendar_events with withCancelled for the affected occurrences. It never says explicitly when to prefer this tool over siblings such as list_calendar_conflicts or when to use set_calendar_pause/delete_calendar_pause instead, leaving routing to inference from names.

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