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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_notification_list

Read-onlyIdempotent

Retrieve calendar notifications for a specific calendar, with filters for active and deleted items and pagination controls to page through results.

Instructions

Get notifications Get calendar notifications based on query Endpoint: GET /calendars/{calendarId}/notifications (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars/events.readonly Pagination params: limit, skip — pass them to page through full result sets.

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

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of records to skip
limitNoNumber of records to return
deletedNoInclude deleted notifications
isActiveNoFilter by active status
calendarIdYesCalendar ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 / deleted / description
      Added value: +"Include deleted notifications"
    • addedInput schema / properties / deleted / example
      Added value: +false
    • addedInput schema / properties / isActive / description
      Added value: +"Filter by active status"
    • addedInput schema / properties / isActive / example
      Added value: +true
    • addedInput schema / properties / limit / example
      Added value: +20
    • addedInput schema / properties / skip / example
      Added value: +0
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld. The description adds context annotations cannot carry: the required OAuth scope (calendars/events.readonly) and the v3 API version/source. Return shape is still unstated, but the auth prerequisite is a meaningful addition.

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?

Four short lines, front-loaded with the purpose before the endpoint and scope metadata. The first line "Get notifications" is redundant with the second, but the overall footprint is efficient.

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 read-only paged list with no output schema, the description covers purpose, endpoint, auth scope and paging. An agent can invoke it correctly; only the filter semantics for deleted/isActive rely on the (fully documented) schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining the purpose of limit/skip as a paging mechanism rather than just naming them. The deleted/isActive filters are left entirely to the schema.

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 ("Get calendar notifications based on query") plus the underlying endpoint GET /calendars/{calendarId}/notifications, which pins down scope. It is distinguishable from the notification get/create/update/delete siblings by the plural list semantics, though the description never says so explicitly.

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?

The pagination sentence tells the agent to pass limit/skip to page through full result sets, which is genuine usage guidance. But it gives no guidance on when to use this list versus ghl_calendar_notification_get for a single notification, and "based on query" is left undefined.

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