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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_schedule_create

Create user availability schedules by defining rules, timezone, location, user, and calendar associations for calendar management.

Instructions

Create user availability schedule Create new schedule with specified rules, timezone, location, user and calendar associations. Endpoint: POST /calendars/schedules (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": {
      "body": "<body>"
    },
    "name": "ghl_calendar_schedule_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

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

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent, open-world operation. The description adds useful context with the endpoint and OAuth scope ('calendars.write'), but it does not explain what is returned, error behavior, or how the new schedule manifests after creation.

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 description is short and front-loaded, with the main purpose first and endpoint/auth details after. The first line largely repeats the title and the second line is somewhat redundant, but there is no excessive prose.

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 create tool with a fully described nested body and no output schema, the description gives the essential operation context, endpoint, and required OAuth scope. It does not cover return values or post-creation behavior, but it is largely sufficient for correct invocation.

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%, and the nested body schema already documents fields such as timezone, locationId, userId, rules, and calendarIds in detail. The description lists the same categories at a high level but adds no meaningful syntax or constraint information beyond the schema.

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 states a specific verb and resource: 'Create user availability schedule' and 'Create new schedule'. It also names the main associated data (rules, timezone, location, user, calendar associations), which distinguishes it from sibling read/update/delete schedule tools.

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 'create' verb implies the tool is used when a new schedule is needed, but the description does not explicitly say when to use it versus alternatives such as ghl_calendar_schedule_update or ghl_calendar_schedule_assign. No exclusions or prerequisites are given beyond the required OAuth scope.

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