Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_calendar_event_schedule_update

Idempotent

Update the availability schedule for an event calendar by calendar ID, changing only the supplied rules or timezone. Use it to adjust recurring weekday or specific-date availability windows.

Instructions

Update event calendar availability schedule Update the availability schedule for a specific event calendar. Only provided fields will be updated. The calendar ID is provided in the path. Endpoint: PUT /calendars/schedules/event-calendar/{calendarId} (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars.write

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": {
      "calendarId": "<calendarId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_event_schedule_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
calendarIdYesUnique identifier of the event calendar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / rules / items / properties / intervals / items / title
      Added value: +"ScheduleIntervalDTO"
    • addedInput schema / properties / body / properties / rules / items / title
      Added value: +"ScheduleRuleDTO"
    • addedInput schema / properties / body / title
      Added value: +"UpdateEventCalendarScheduleDTO"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-readOnly, but the description adds material context beyond them: the required OAuth scope (calendars.write) and the partial-PATCH semantics of only updating supplied fields. It does not mention irreversibility of replacing rules or rate limits, so not 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.

Conciseness4/5

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

Purpose and the partial-update rule are front-loaded in the first two sentences. The trailing endpoint/version/source metadata is somewhat verbose but does convey the HTTP shape; overall efficient.

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 2-parameter update with a nested body, no output schema, and rich annotations, the description covers destination, scope, and update semantics adequately. A note on whether rules replace or merge would have closed the remaining gap.

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 100%, so nested rule/interval/timezone semantics are already documented in the schema. The description only adds that calendarId is taken from the path, which is marginal extra value — baseline 3 applies.

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 ('Update the availability schedule for a specific event calendar'), which is distinguishable from the sibling ghl_calendar_schedule_update because it is scoped to an event calendar keyed by calendarId. An agent can select this without opening the schema.

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?

Adds the useful invocation rule 'Only provided fields will be updated' and notes the calendar ID is in the path, which shapes how to call it. However, it gives no guidance on when to prefer this over ghl_calendar_schedule_update or ghl_calendar_event_schedule_create, and no prerequisites beyond the scope string.

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

Deploy Server

Other Tools