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

ghl-mcp-server-v2

by zackscriven

ghl_calendar_service_create

Creates a new calendar service in a location with assigned staff, pricing, duration, buffers, and optional variations for booking.

Instructions

Create Service Create new service in a location. Endpoint: POST /calendars/services/catalog (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": {
      "body": "<body>"
    },
    "name": "ghl_calendar_service_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / payment / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "amount": {
      -        "description": "Service price",
      -        "example": 50,
      -        "type": "number"
      -      },
      -      "deposit": {
      -        "description": "Deposit amount or percentage value",
      -        "example": 20,
      -        "type": "number"
      -      },
      -      "depositType": {
      -        "description": "Deposit type",
      -        "enum": [
      -          "percentage",
      -          "amount"
      -        ],
      -        "example": "amount",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "amount": {
      +        "description": "Service price",
      +        "example": 50,
      +        "type": "number"
      +      },
      +      "deposit": {
      +        "description": "Deposit amount or percentage value",
      +        "example": 20,
      +        "type": "number"
      +      },
      +      "depositType": {
      +        "description": "Deposit type",
      +        "enum": [
      +          "percentage",
      +          "amount"
      +        ],
      +        "example": "amount",
      +        "type": "string"
      +      }
      +    },
      +    "title": "PaymentDTO",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / properties / payment / example
      Added value: +{
      +  "amount": 50,
      +  "deposit": 20,
      +  "depositType": "amount"
      +}
    • addedInput schema / properties / body / properties / staff / example
      Added value: +[
      +  {
      +    "id": "65e5f6dfacf123513228d384"
      +  }
      +]
    • addedInput schema / properties / body / properties / staff / items / title
      Added value: +"StaffDTO"
    • addedInput schema / properties / body / properties / variations / example
      Added value: +[
      +  {
      +    "name": "Standard Haircut",
      +    "payment": {
      +      "amount": 50
      +    },
      +    "serviceDuration": 30
      +  }
      +]
    • changedInput schema / properties / body / properties / variations / items / properties / payment / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "amount": {
      -        "description": "Service price",
      -        "example": 50,
      -        "type": "number"
      -      },
      -      "deposit": {
      -        "description": "Deposit amount or percentage value",
      -        "example": 20,
      -        "type": "number"
      -      },
      -      "depositType": {
      -        "description": "Deposit type",
      -        "enum": [
      -          "percentage",
      -          "amount"
      -        ],
      -        "example": "amount",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "amount": {
      +        "description": "Service price",
      +        "example": 50,
      +        "type": "number"
      +      },
      +      "deposit": {
      +        "description": "Deposit amount or percentage value",
      +        "example": 20,
      +        "type": "number"
      +      },
      +      "depositType": {
      +        "description": "Deposit type",
      +        "enum": [
      +          "percentage",
      +          "amount"
      +        ],
      +        "example": "amount",
      +        "type": "string"
      +      }
      +    },
      +    "title": "PaymentDTO",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / properties / variations / items / properties / payment / example
      Added value: +{
      +  "amount": 50,
      +  "deposit": 20,
      +  "depositType": "amount"
      +}
    • addedInput schema / properties / body / properties / variations / items / title
      Added value: +"CreateServiceVariationDTO"
    • addedInput schema / properties / body / title
      Added value: +"CreateServiceDTO"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true. The description adds genuinely useful context beyond them: the exact endpoint and the required OAuth scope 'calendars.write'. However, it says nothing about slug uniqueness enforcement, validation failures, or what is returned after creation.

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?

Front-loaded with the action, then endpoint and scope metadata. Four short lines, no padding; the source-spec reference is slightly developer-oriented but still informative.

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 create tool with no output schema, the description covers the action, endpoint, and auth scope, and annotations cover the safety profile. The notable remaining gap is that it does not indicate what the response contains (e.g., the new service ID) for a non-idempotent create.

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 CreateServiceDTO documents every field with examples, so the schema carries the parameter burden. The description adds nothing about the body (e.g., required locationId, staff minimum of one), so baseline 3 applies.

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 gives a specific verb and resource: 'Create new service in a location', which cleanly separates it from ghl_calendar_service_get/list/update/delete siblings. It does not explicitly name sibling alternatives, but the create semantics are unmistakable.

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 implied by the verb ('create new service in a location') and the OAuth scope line signals the required permission, but there is no explicit guidance on when to use this versus service_update or service_location_create, nor any stated prerequisites beyond the scope.

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