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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_schedule_update

Idempotent

Update an existing user availability schedule by changing its rules, timezone, or name; only provided fields are modified.

Instructions

Update user availability schedule Modify an existing schedule by updating its rules, timezone, and name All fields are optional - only provided fields will be updated. Endpoint: PUT /calendars/schedules/{id} (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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "ghl_calendar_schedule_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the schedule to update
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: +"UpdateScheduleDTO"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the safety profile is covered; the description adds genuinely new context: the PUT endpoint, the required calendars.write OAuth scope, and the partial-update rule that omitted fields are left untouched. It does not disclose whether supplying `rules` replaces the entire rule set or merges, which is the main behavioral risk for this nested array.

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?

Front-loaded with purpose in the first line, followed by the partial-update caveat and then operational metadata (endpoint, version, scope). Slightly redundant opening ("Update user availability schedule" then "Modify an existing schedule"), and the source-file note is noise for an agent, but nothing is bloated.

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 mutation tool with a deeply nested rules payload and no output schema, the description covers purpose, auth scope, and partial-update behavior, and the schema carries all field-level detail. The missing piece is how the rules array interacts with existing rules on update, which matters given the nested structure.

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 id, name, timezone and the full nested rule/interval structure are already documented in the schema. The description only restates the three body fields by name and adds no format, constraint, or merge-semantics detail beyond what the schema provides, so the baseline of 3 applies.

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 (update/modify) and resource (user availability schedule) and enumerates the mutable fields (rules, timezone, name), so an agent can distinguish it from ghl_calendar_schedule_create or _get. It never names a sibling or clarifies the boundary with adjacent tools like ghl_calendar_update or ghl_calendar_schedule_assign, so it stops short of a 5.

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?

"Modify an existing schedule" plus the required {id} implies this is only for schedules that already exist, and "only provided fields will be updated" gives partial-update guidance. However, there is no explicit when-to-use/when-not, no statement of prerequisites (must the schedule already be assigned? does create have to happen first?), and no pointer to alternatives.

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