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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_notification_get

Read-onlyIdempotent

Retrieves a specific calendar event notification by calendar ID and notification ID so you can inspect its details from GoHighLevel.

Instructions

Get notification Find Event notification by notificationId Endpoint: GET /calendars/{calendarId}/notifications/{notificationId} (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": {
      "calendarId": "<calendarId>",
      "notificationId": "<notificationId>"
    },
    "name": "ghl_calendar_notification_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendarIdYesCalendar ID
notificationIdYesNotification ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • 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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld; the description adds genuinely new operational context by naming the required OAuth scope (calendars/events.readonly) and the API version header, which an agent needs to authorize the call. It still says nothing about not-found behavior or the shape of the payload.

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 and the identifying parameter, followed by endpoint and scope in compact form. The 'source: v3/calendars-v3.json' metadata is filler but the overall length is tight.

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?

With no output schema, the description carries the burden of describing what comes back, and it does not say anything about the returned notification fields or error cases. For a simple two-parameter read with full schema coverage and strong annotations that is a gap but not a blocking one.

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 coverage is 100% and both parameters carry descriptions plus examples, so the schema does the documentation work. The description only reinforces that notificationId identifies the target; 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: retrieve a single event notification by notificationId, and gives the exact endpoint GET /calendars/{calendarId}/notifications/{notificationId}. This distinguishes it from the list/create/update/delete notification siblings, though the phrasing 'Get notification / Find Event notification' is slightly redundant.

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?

Usage is implied by 'by notificationId' — an agent infers it is for fetching one known notification rather than listing. However, it never explicitly says when to prefer this over ghl_calendar_notification_list or what to do when only a calendar is known.

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