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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_resource_list

Read-onlyIdempotent

Retrieve calendar resources by resource type and location ID, with limit and skip pagination, to page through rooms or equipment for a sub-account.

Instructions

Uses the currently-documented (non-deprecated) Calendar Resources version, 2021-04-15. The v3-tagged variant of this operation in the v3 spec is marked deprecated (Services V1) with identical request/response fields — do not use Version: v3 for resource endpoints. List Calendar Resources List calendar resources by resource type and location ID (Services V1) Endpoint: GET /calendars/resources/{resourceType} (Version header: v3; source: v3/calendars-v3.json) Requires a Sub-Account (location) token. OAuth scopes: calendars/resources.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": {
      "resourceType": "<resourceType>",
      "locationId": "<locationId>",
      "limit": "<limit>",
      "skip": "<skip>"
    },
    "name": "ghl_calendar_resource_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipYesNumber of results to skip
limitYesMaximum number of results
locationIdYesLocation ID
resourceTypeYesCalendar Resource Type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.1.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results"
    • addedInput schema / properties / limit / example
      Added value: +20
    • addedInput schema / properties / locationId / description
      Added value: +"Location ID"
    • addedInput schema / properties / locationId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / resourceType / example
      Added value: +"equipments"
    • addedInput schema / properties / skip / description
      Added value: +"Number of results to skip"
    • addedInput schema / properties / skip / example
      Added value: +0
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety bar is low. The description still adds real context beyond them: it requires a Sub-Account (location) token, specifies the OAuth scope calendars/resources.readonly, and explains pagination semantics.

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 content is useful but the structure buries the purpose behind a versioning preamble, an endpoint citation, and a source-file reference (v3/calendars-v3.json). Several phrases restate the same deprecation warning, and the source-path detail is noise for an agent choosing a tool.

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 list endpoint with no output schema, the description covers the essentials: auth token type, OAuth scope, required filters, endpoint, and pagination. Only the shape of the returned resource objects is left unstated, which is a minor gap since no output schema exists.

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%, with descriptions, examples, and an enum on resourceType, so the baseline is 3. The description earns an extra point by explaining that limit and skip are pagination controls meant to be passed together to traverse the full result set, which is more than the schema's one-line field notes.

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 and resource: 'List calendar resources by resource type and location ID', and the endpoint line confirms the exact path. It is clearly distinguishable from the sibling get/create/update/delete resource tools, though the leading paragraph is about API versioning rather than purpose, so the core purpose is not front-loaded.

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

Usage Guidelines4/5

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

It gives an explicit when-not: do not use Version: v3 for resource endpoints because that variant is deprecated, and it instructs the caller to pass limit and skip to page through full result sets. It does not compare against sibling tools, but the version/endpoint selection guidance is unusually concrete.

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