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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_resource_get

Read-onlyIdempotent

Retrieve a calendar room or equipment resource by ID and resource type with a sub-account token to verify details for scheduling and availability.

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. Get Calendar Resource Get calendar resource by ID (Services V1) Endpoint: GET /calendars/resources/{resourceType}/{id} (Version header: v3; source: v3/calendars-v3.json) Requires a Sub-Account (location) token. OAuth scopes: calendars/resources.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": {
      "resourceType": "<resourceType>",
      "id": "<id>"
    },
    "name": "ghl_calendar_resource_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCalendar Resource ID
resourceTypeYesCalendar Resource Type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / id / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / resourceType / example
      Added value: +"equipments"
  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?

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses auth prerequisites: a Sub-Account (location) token and the calendars/resources.readonly OAuth scope. That is genuinely additive context. It does not describe the response payload, but for a simple read this is a minor gap.

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?

Roughly half the text is a versioning/deprecation digression that leads the description instead of the actual purpose. It also reads self-conflicting ('do not use Version: v3' immediately followed by 'Version header: v3'), which costs clarity, though the endpoint and scope lines earn their place.

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 two-parameter read tool with full schema coverage and no output schema, the definition covers endpoint, auth token type, and OAuth scope. The only meaningful omission is any hint of the returned resource shape, which is low-stakes 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?

Schema description coverage is 100% and resourceType carries an enum, so the schema does the documenting. The endpoint template restates that resourceType and id are path parameters but adds no format or validation detail beyond the schema, matching the baseline 3.

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 ('Get Calendar Resource by ID', GET /calendars/resources/{resourceType}/{id}'), which distinguishes it from the list/update/create/delete resource siblings. It is clear but the purpose is buried behind versioning preamble rather than leading with what the tool does.

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?

It gives real guidance on which API version to target ('do not use Version: v3 for resource endpoints'), which is useful. However, it never states when to reach for this tool versus ghl_calendar_resource_list or the update/delete variants, so the sibling-choice guidance is only implied by 'by ID'.

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