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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_appointment_update

Idempotent

Update an existing calendar appointment by event ID, including title, times, status, location, and recurrence settings.

Instructions

Update Appointment Update appointment Endpoint: PUT /calendars/events/appointments/{eventId} (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars/events.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": {
      "eventId": "<eventId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_appointment_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
eventIdYesEvent Id or Instance id. For recurring appointments send masterEventId to modify original series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / appointmentStatus / description
      Added value: +"Appointment status"
    • addedInput schema / properties / body / properties / rrule / example
      Added value: +"RRULE:FREQ=DAILY;INTERVAL=1;COUNT=5"
    • addedInput schema / properties / body / title
      Added value: +"AppointmentEditSchema"
    • addedInput schema / properties / eventId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation profile is covered. The description adds genuinely useful non-schema facts: the write scope calendars/events.write and the v3 version header. However, it says nothing about side effects such as whether unsupplied fields are cleared, whether notifications fire, or how recurring-instance updates propagate.

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

Conciseness3/5

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

It is short, but the title and name are duplicated verbatim in the first two lines, which wastes the most valuable front-loaded position. The endpoint, version, and scope lines do earn their place; a single sentence stating the update semantics would have been a better lead.

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 PUT mutation with a fully annotated schema, no output schema, and annotations covering safety, the description supplies the endpoint, API version, and required OAuth scope, which is close to sufficient for correct invocation. The remaining gap is semantic: whether this is a full replacement or a partial update is never stated.

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 documents all 14 fields including the rrule/ignoreFreeSlotValidation interaction and the meetingLocation override rules, so the schema carries the parameter burden. The description adds no parameter meaning beyond naming {eventId} implicitly through the endpoint path.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs the verb 'Update' with the resource 'Appointment' and adds the concrete endpoint (PUT /calendars/events/appointments/{eventId}), which does pin down which resource is mutated. But it never distinguishes this from close siblings such as ghl_calendar_appointment_create, ghl_calendar_event_delete, or ghl_calendar_block_slot_update, and the first two lines simply restate the tool name and title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, no preconditions, and no note on when a create/get/delete sibling is the better choice. The only context offered is the endpoint and OAuth scope, which tells an agent nothing about selection criteria.

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