Chronary

Official

Overview Schema Related Servers Score Discussions

set_availability_rules

Idempotent

Define buffer times before and after events and set per-day working hours to automatically apply to availability queries.

Instructions

Set or replace the availability rules on a calendar — buffer times before/after events and optional per-day working hours. When these rules are set, every availability query on this calendar automatically applies them (busy-block expansion for buffers, masking outside working hours). Upsert: overwrites any existing rules.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`timezone`	No	IANA timezone used to interpret working_hours (e.g. America/New_York)	UTC
`calendar_id`	Yes	Calendar to configure
`working_hours`	No	Per-day working hours map in the calendar's timezone; omit keys for off-days. Pass null to remove any working-hours constraint.
`buffer_after_minutes`	No	Minutes of buffer after each event (0–120)
`buffer_before_minutes`	No	Minutes of buffer before each event (0–120)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedv1.2.6Jul 7, 2026

changedInput schema / properties / working_hours / anyOf

Previous value: -[
-  {
-    "properties": {
-      "fri": {
-        "description": "A single day's working hours window",
-        "properties": {
-          "end": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          },
-          "start": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "start",
-          "end"
-        ],
-        "type": "object"
-      },
-      "mon": {
-        "description": "A single day's working hours window",
-        "properties": {
-          "end": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          },
-          "start": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "start",
-          "end"
-        ],
-        "type": "object"
-      },
-      "sat": {
-        "description": "A single day's working hours window",
-        "properties": {
-          "end": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          },
-          "start": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "start",
-          "end"
-        ],
-        "type": "object"
-      },
-      "sun": {
-        "description": "A single day's working hours window",
-        "properties": {
-          "end": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          },
-          "start": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "start",
-          "end"
-        ],
-        "type": "object"
-      },
-      "thu": {
-        "description": "A single day's working hours window",
-        "properties": {
-          "end": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          },
-          "start": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "start",
-          "end"
-        ],
-        "type": "object"
-      },
-      "tue": {
-        "description": "A single day's working hours window",
-        "properties": {
-          "end": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          },
-          "start": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "start",
-          "end"
-        ],
-        "type": "object"
-      },
-      "wed": {
-        "description": "A single day's working hours window",
-        "properties": {
-          "end": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          },
-          "start": {
-            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
-            "type": "string"
-          }
-        },
-        "required": [
-          "start",
-          "end"
-        ],
-        "type": "object"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "fri": {
+        "description": "A single day's working hours window",
+        "properties": {
+          "end": {
+            "description": "End of the working window, HH:MM 24-hour, after start (e.g. \"17:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          },
+          "start": {
+            "description": "Start of the working window, HH:MM 24-hour, in the rules timezone (e.g. \"09:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "mon": {
+        "description": "A single day's working hours window",
+        "properties": {
+          "end": {
+            "description": "End of the working window, HH:MM 24-hour, after start (e.g. \"17:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          },
+          "start": {
+            "description": "Start of the working window, HH:MM 24-hour, in the rules timezone (e.g. \"09:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "sat": {
+        "description": "A single day's working hours window",
+        "properties": {
+          "end": {
+            "description": "End of the working window, HH:MM 24-hour, after start (e.g. \"17:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          },
+          "start": {
+            "description": "Start of the working window, HH:MM 24-hour, in the rules timezone (e.g. \"09:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "sun": {
+        "description": "A single day's working hours window",
+        "properties": {
+          "end": {
+            "description": "End of the working window, HH:MM 24-hour, after start (e.g. \"17:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          },
+          "start": {
+            "description": "Start of the working window, HH:MM 24-hour, in the rules timezone (e.g. \"09:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "thu": {
+        "description": "A single day's working hours window",
+        "properties": {
+          "end": {
+            "description": "End of the working window, HH:MM 24-hour, after start (e.g. \"17:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          },
+          "start": {
+            "description": "Start of the working window, HH:MM 24-hour, in the rules timezone (e.g. \"09:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "tue": {
+        "description": "A single day's working hours window",
+        "properties": {
+          "end": {
+            "description": "End of the working window, HH:MM 24-hour, after start (e.g. \"17:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          },
+          "start": {
+            "description": "Start of the working window, HH:MM 24-hour, in the rules timezone (e.g. \"09:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "wed": {
+        "description": "A single day's working hours window",
+        "properties": {
+          "end": {
+            "description": "End of the working window, HH:MM 24-hour, after start (e.g. \"17:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          },
+          "start": {
+            "description": "Start of the working window, HH:MM 24-hour, in the rules timezone (e.g. \"09:00\")",
+            "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "start",
+          "end"
+        ],
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv1.2.5Jul 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the description's mention of 'Upsert: overwrites any existing rules' and the effect on availability queries adds some context but does not significantly extend beyond the annotations. No side effects beyond overwriting are disclosed, and the impact on existing events is not clarified.

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

Conciseness5/5

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

The description is three sentences long, front-loaded with the core purpose, followed by the effect on queries and the overwrite behavior. No extraneous information; every sentence earns its 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?

Given the tool has 5 parameters and no output schema, the description covers the main behavior: setting buffers and working hours, their automatic application, and the upsert nature. It could mention that working hours are optional or that timezone defaults to UTC, but the schema handles that. Overall, it is sufficiently complete for a setter tool.

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 mentions 'buffer times before/after events and optional per-day working hours', which aligns with parameters but does not add detailed semantics beyond what the schema already provides. The parameter descriptions in the schema are already comprehensive.

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?

The description clearly states the tool's verb ('Set or replace'), the resource ('availability rules on a calendar'), and the specific behaviors ('buffer times before/after events and optional per-day working hours'). It distinguishes itself from sibling tools like 'clear_availability_rules' and 'get_availability_rules' by focusing on setting/replacing rules.

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?

The description provides context on when the rules take effect ('every availability query on this calendar automatically applies them') and notes the upsert behavior ('overwrites any existing rules'). However, it does not explicitly state when to use this tool versus alternatives, such as when to use 'clear_availability_rules' for removal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Chronary/chronary-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server