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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_appointment_get

Read-onlyIdempotent

Fetch a specific calendar appointment by its event ID to retrieve full schedule details and event information.

Instructions

Get Appointment Get appointment by ID Endpoint: GET /calendars/events/appointments/{eventId} (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars/events.readonly

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>"
    },
    "name": "ghl_calendar_appointment_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent Id or Instance id. For recurring appointments send masterEventId to modify original series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / eventId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world. The description adds the OAuth scope and API endpoint/version, which is useful auth and behavior context, but it does not describe the response or any rate limits.

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 core purpose is stated in the first line and the extra endpoint/version details are compact. The 'source: v3/calendars-v3.json' line is developer metadata that does not help the agent and slightly reduces conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with full schema coverage and rich annotations, the description covers endpoint, scope, and version. It lacks any statement about the returned appointment shape, and the schema's 'modify original series' note is left unaddressed, which is a completeness gap for a read-only getter.

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?

The schema fully documents eventId at 100% coverage, so the description need not add parameter detail. The description mentions the endpoint path with {eventId} but adds no new meaning, and it does not clarify the schema's confusing note about modifying recurring series on a read-only get.

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?

The description states a specific verb ('Get') and resource ('Appointment') and specifies retrieval by ID, which is clear. It does not explicitly differentiate from sibling read tools such as event lists or note lists, though the name and 'by ID' make the purpose obvious.

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?

No guidance is given on when to use this tool versus alternatives; the endpoint and OAuth scope are technical metadata, not usage selection advice. The agent must infer that it should be used when an eventId is known and a single appointment is needed.

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