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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_block_slot_update

Idempotent

Update an existing calendar block slot by event ID to change its title, time range, calendar or assigned user, and location.

Instructions

Update Block Slot Update block slot by ID Endpoint: PUT /calendars/events/block-slots/{eventId} (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars/events.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": {
      "eventId": "<eventId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_block_slot_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
eventIdYesEvent Id or Instance id. For recurring appointments send masterEventId to modify original series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"BlockSlotEditRequestDTO"
    • addedInput schema / properties / eventId / example
      Added value: +"ocQHyuzHvysMo5N5VsXc"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent write, so the safety profile is covered. The description adds genuinely useful operational context — the OAuth scope calendars/events.write and the v3 endpoint path — but never clarifies that PUT implies full replacement of the slot (calendarId/locationId are required), which is the key behavioral risk.

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?

The action is front-loaded in the first line, with endpoint and scope metadata following as compact reference lines. The 'source: v3/calendars-v3.json' provenance string is mostly noise, keeping it from a 5.

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 tool with no output schema, the description supplies endpoint and auth scope but not the PUT-replacement implication or what fields can be changed. The nested body schema fills some of the gap, so it is adequate but not complete.

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%, including eventId's masterEventId note for recurring events, so the schema carries parameter meaning. The description adds no parameter-level detail beyond the path template, 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 specific verb and resource ('Update block slot by ID') plus the exact endpoint PUT /calendars/events/block-slots/{eventId}, so an agent knows precisely what happens. It does not explicitly contrast with ghl_calendar_block_slot_create, but the update-by-ID framing makes the distinction reasonably apparent.

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 only implied: 'by ID' suggests an existing block slot must be selected first, but the description never states when to choose this over block_slot_create or the delete/list siblings, nor any prerequisites like needing a valid eventId.

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