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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_notification_update

Idempotent

Updates a calendar event notification by ID, letting you change its channel, timing, template, recipients, and active status.

Instructions

Update notification Update Event notification by id Endpoint: PUT /calendars/{calendarId}/notifications/{notificationId} (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": {
      "calendarId": "<calendarId>",
      "notificationId": "<notificationId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_notification_update"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / afterTime / items / properties / timeOffset / description
      Added value: +"Time offset value for the notification schedule"
    • addedInput schema / properties / body / properties / afterTime / items / properties / timeOffset / example
      Added value: +1
    • addedInput schema / properties / body / properties / afterTime / items / properties / unit / description
      Added value: +"Unit of time for the offset"
    • addedInput schema / properties / body / properties / afterTime / items / properties / unit / example
      Added value: +"hours"
    • addedInput schema / properties / body / properties / afterTime / items / title
      Added value: +"SchedulesDTO"
    • addedInput schema / properties / body / properties / beforeTime / items / properties / timeOffset / description
      Added value: +"Time offset value for the notification schedule"
    • addedInput schema / properties / body / properties / beforeTime / items / properties / timeOffset / example
      Added value: +1
    • addedInput schema / properties / body / properties / beforeTime / items / properties / unit / description
      Added value: +"Unit of time for the offset"
    • addedInput schema / properties / body / properties / beforeTime / items / properties / unit / example
      Added value: +"hours"
    • addedInput schema / properties / body / properties / beforeTime / items / title
      Added value: +"SchedulesDTO"
    • addedInput schema / properties / body / properties / body / example
      Added value: +"Your appointment has been confirmed."
    • addedInput schema / properties / body / properties / channel / example
      Added value: +"email"
    • addedInput schema / properties / body / properties / deleted / example
      Added value: +false
    • addedInput schema / properties / body / properties / fromAddress / example
      Added value: +"notifications@example.com"
    • addedInput schema / properties / body / properties / fromName / example
      Added value: +"Acme Scheduling"
    • addedInput schema / properties / body / properties / fromNumber / example
      Added value: +"+15551234567"
    • addedInput schema / properties / body / properties / isActive / example
      Added value: +true
    • addedInput schema / properties / body / properties / notificationType / example
      Added value: +"confirmation"
    • addedInput schema / properties / body / properties / receiverType / example
      Added value: +"user"
    • addedInput schema / properties / body / properties / subject / example
      Added value: +"Appointment Confirmation"
    • addedInput schema / properties / body / properties / templateId / example
      Added value: +"MwPcayliwcdoUFzvbTok"
    • addedInput schema / properties / body / title
      Added value: +"UpdateCalendarNotificationsDTO"
    • addedInput schema / properties / calendarId / description
      Added value: +"Calendar ID"
    • addedInput schema / properties / calendarId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / notificationId / description
      Added value: +"Notification ID"
    • addedInput schema / properties / notificationId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds real extra context — the OAuth scope calendars/events.write, which tells the agent what credential is required. However, it says nothing about update semantics (full replace vs partial merge of the notification body), which is the most consequential unknown for a PUT mutation.

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?

The first line 'Update notification' merely restates the annotation title against a line that immediately repeats the same idea ('Update Event notification by id'). The endpoint, version/source and scope lines are compact and useful, but the leading duplication is waste in a five-line description.

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 mutation with a large nested body object that has no required inner properties, the definition never explains which fields must be supplied or what an omitted field does. Annotations and a fully described schema cover a lot, and there is no output schema so return values need not be explained, but the update/replace semantics gap keeps this at minimum-viable.

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 every body field carries its own description and example, so the schema does the heavy lifting. The description contributes nothing about parameters beyond the endpoint template that shows calendarId and notificationId in the path. Baseline 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 and resource ('Update Event notification by id') plus the exact endpoint PUT /calendars/{calendarId}/notifications/{notificationId}, so the operation is unambiguous. It does not explicitly contrast itself with the sibling create/delete/get/list notification tools, but the combination of verb + 'by id' + endpoint is sufficient to distinguish it.

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 when-to-use statement and no mention of alternatives (ghl_calendar_notification_create, _delete, _get are siblings). The agent must infer from 'by id' that this modifies an existing notification rather than creating one. No prerequisites or conditions are given beyond the 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