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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_event_schedule_create

Creates a new availability schedule for an event calendar by specifying rules and timezone.

Instructions

Create event calendar availability schedule Create a new availability schedule specifically for an event calendar. The calendar ID is provided in the path, and schedule rules and timezone are provided in the request body. Endpoint: POST /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_create"
  }
}

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: +"CreateEventCalendarScheduleDTO"
  2. First observedv2.0.0

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, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the mutation profile is covered. The description adds the OAuth scope (calendars.write) and API version header, which are useful, but it does not disclose duplicate-handling behavior (relevant given idempotentHint=false) or failure modes.

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 purpose is front-loaded in the first two sentences and the endpoint/scope metadata is compact. The leading fragment 'Create event calendar availability schedule' duplicates the title slightly but costs little.

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 nested-object create with no output schema, the fully documented schema plus annotations leave little the description must carry. Adding the scope and endpoint makes it self-sufficient; only the interaction with the general schedule tool remains unexplained.

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%, with rules, intervals, day/date, and IANA timezone all documented inline with examples and patterns. The description only restates which param goes in the path vs body, adding minimal meaning beyond the schema — baseline 3 is appropriate.

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 a specific verb and resource — create a new availability schedule for an event calendar — and the term 'event calendar' implicitly distinguishes it from the general ghl_calendar_schedule_create sibling. It stops short of naming that sibling, so the differentiation is inferable rather than explicit.

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?

The description clarifies where inputs go (calendarId in path, rules/timezone in body) and gives the endpoint and required OAuth scope, which implies when it can be used. But it never says when to prefer this over ghl_calendar_schedule_create or what prerequisites must exist (e.g., the calendar must first be created).

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