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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_resource_update

Idempotent

Updates an existing calendar resource by ID for rooms or equipment, letting you change details such as name, capacity, active status, quantity, and calendar mappings.

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

Input Schema

NameRequiredDescriptionDefault
idYesCalendar Resource ID
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
resourceTypeYesCalendar Resource Type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / calendarIds / example
      Added value: +[
      +  "Jsj0xnlDDjw0SuvX1J13"
      +]
    • addedInput schema / properties / body / properties / capacity / example
      Added value: +20
    • addedInput schema / properties / body / properties / description / description
      Added value: +"Description of the calendar resource"
    • addedInput schema / properties / body / properties / description / example
      Added value: +"Main conference room projector"
    • addedInput schema / properties / body / properties / locationId / description
      Added value: +"Location ID"
    • addedInput schema / properties / body / properties / locationId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / body / properties / name / description
      Added value: +"Name of the calendar resource"
    • addedInput schema / properties / body / properties / name / example
      Added value: +"Projector"
    • addedInput schema / properties / body / properties / outOfService / example
      Added value: +1
    • addedInput schema / properties / body / properties / quantity / example
      Added value: +5
    • addedInput schema / properties / body / title
      Added value: +"UpdateCalendarResourceDTO"
    • addedInput schema / properties / id / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
    • addedInput schema / properties / resourceType / example
      Added value: +"equipments"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, so the description only needs to add context; it supplies the Sub-Account (location) token requirement and the exact OAuth scope 'calendars/resources.write', which is real operational information an agent cannot get from annotations. It stops short of explaining PUT partial-vs-full replacement semantics, which is the one behavior that would matter most here.

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 description opens with two dense sentences of version/deprecation plumbing before stating what the tool does, so the core purpose is not front-loaded. The version guidance is repetitive ('non-deprecated' vs 'v3... identical request/response fields') and could be compressed to one clause without losing information.

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 annotations, no output schema, and a fully documented nested body, the description covers auth and scope well. It omits whether unspecified body fields are preserved or cleared on this idempotent PUT, which is the main unanswered question an agent would have before invoking it.

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 the nested DTO documents every field including the equipment-vs-room calendarIds constraint, so the schema carries parameter meaning. The description adds no field-level guidance, leaving the baseline 3 appropriate.

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 concrete verb and resource ('Update calendar resource by ID (Services V1)') and pins the endpoint path, so an agent can distinguish it from ghl_calendar_resource_create/get by the ID-based update semantics. It never names the sibling tools directly, so differentiation is inferential rather than explicit.

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 only usage direction is version selection ('do not use Version: v3 for resource endpoints'), which is genuinely actionable but concerns spec versioning, not when to pick this tool over ghl_calendar_resource_create or ghl_calendar_resource_get. No prerequisites or exclusion conditions for the update operation itself are given.

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