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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_service_location_update

Idempotent

Update an existing service location's details, including name, slug, phone, address, cover image, and location type, by service location ID.

Instructions

Update Service Location Update an existing service location Endpoint: PUT /calendars/services/locations/{serviceLocationId} (Version header: v3; source: v3/calendars-v3.json) OAuth scopes: calendars.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": {
      "serviceLocationId": "<serviceLocationId>",
      "body": "<body>"
    },
    "name": "ghl_calendar_service_location_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
serviceLocationIdYesUnique Service Location ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateServiceLocationDTO"
  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 the mutation profile: not read-only, idempotent, non-destructive, and open-world. The description adds useful context beyond that by naming the OAuth scope calendars.write and the exact PUT endpoint/API version, although it does not explain whether omitted body fields are preserved or cleared.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded: purpose first, then endpoint and auth scope. The first two lines are slightly redundant but still compact and waste little space.

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 an update tool with complete schema descriptions and annotations covering safety/idempotency, the description supplies endpoint and auth scope. It could mention partial-update behavior, but otherwise it gives enough to call the tool correctly.

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%, so the schema already documents both serviceLocationId and all nested body fields. The description adds the path shape for serviceLocationId but does not add meaning beyond the schema for the body fields.

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: 'Update an existing service location.' That is clearer than the tool name alone and distinguishes it from create/get/list siblings, though it does not explicitly contrast it with ghl_calendar_service_location_create or ghl_calendar_service_location_delete.

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 PUT endpoint and 'Update an existing service location' imply that this tool modifies an existing location, but there is no explicit guidance on when to choose it over the create/delete siblings or whether it supports partial updates.

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