Skip to main content
Glama

Reserve Time Slot

reserve_slot
DestructiveIdempotent

Reserve a time slot on an active configured calendar. Returns a pending_offer reservation and tries to send a 6-digit confirmation code to the customer's email or phone. The reservation expires in 15 minutes if not confirmed. Idempotent: re-using the same idempotency_key returns the original reservation and sends no code. If a send could not be confirmed, confirmation.delivered is false and not_sent_reason says whether a code may still arrive. At a business that takes a deposit for agent bookings, pass the offer_id from get_quote (without it the answer is quote_required); no code is sent and the result's payment block carries the amount to pay instead. If the result includes customer_notice, show it to the customer word for word.

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": {
      "slug": "<slug>",
      "window_start": "<window_start>",
      "window_end": "<window_end>",
      "customer_contact": "<customer_contact>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "reserve_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug identifier
agent_idNoOptional agent identifier
offer_idNoOptional id of a signed get_quote offer to redeem against this reservation. Omit for a business with no exact-priced service — authentication is a capability upgrade here, never a toll.
window_endYesSlot end (Unix seconds, an absolute instant) — the matching get_availability slot's `end`; see window_start.
window_startYesSlot start (Unix seconds, an absolute instant). Take it from a get_availability slot: that response carries the business's `timezone`, so request a wide availability window there and filter the returned slots locally rather than guessing the zone.
idempotency_keyYesUnique key for idempotent reservation
customer_contactYesHow to reach the customer. MUST include at least one of email or phone — the confirmation code is delivered there, and a hold nobody can confirm is unreachable from both sides. Email is used when both are present.

Output Schema

NameRequiredDescriptionDefault
statusYesReservation state — 'pending_offer' on a fresh hold; a replay returns the existing row's state
paymentNoAlways present. required:false — confirm with the code (confirmation.method 'otp'). required:true — the customer pays amount_cents (currency) to confirm; balance_due_cents is paid at the visit.
expires_atYesISO-8601. When this hold lapses if it is not confirmed (by code, or by payment when payment.required)
confirmationYes
reservation_idYes
booking_detailsNoFor configured calendars: present these fixed booking details to the customer before confirming their code. No owner approval is required.
customer_noticeNoA sentence for the customer. When present, show it to them word for word.
idempotent_replayNoPresent and true when this idempotency_key already had a reservation; no new code was sent
booking_authorizationNoPresent this summary and booking_details to the customer and obtain explicit agreement before passing its reference to confirm_booking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / customer_notice
      Added value: +{
      +  "description": "A sentence for the customer. When present, show it to them word for word.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / confirmation / properties / channel / description
      Previous value: -"The channel this call used for the code: 'email' or 'sms', whether or not the send was confirmed (see delivered). 'none' when it used none: on an idempotent replay, with method 'payment', or when no channel could reach this contact"New value: +"The channel this call chose for the code: 'email' or 'sms'. It does not say a send was attempted or confirmed; delivered and not_sent_reason say that. 'none' when it chose none: on an idempotent replay, with method 'payment', or when the email send budget refused and the contact left no usable phone"
  3. Changed4 schema fields changed
    • changedOutput schema / properties / confirmation / properties / channel / description
      Previous value: -"Where the code went: 'email', 'sms', or 'none' if delivery was unavailable"New value: +"The channel this call used for the code: 'email' or 'sms', whether or not the send was confirmed (see delivered). 'none' when it used none: on an idempotent replay, with method 'payment', or when no channel could reach this contact"
    • changedOutput schema / properties / confirmation / properties / delivered / description
      Previous value: -"False means nothing confirmed that a code went on this call, and the booking cannot be confirmed until one reaches the customer. On an idempotent replay it is always false, because a replay sends nothing: the first call's answer stands"New value: +"With method 'otp', false means nothing confirmed that a code went on this call, and the booking cannot be confirmed until one reaches the customer. On an idempotent replay it is always false, because a replay sends nothing: the first call's answer stands. With method 'payment' it is always false, because no code is sent"
    • changedOutput schema / properties / confirmation / properties / method / description
      Previous value: -"'otp': a 6-digit code was sent to the customer. 'payment': no code — this booking is confirmed by paying the deposit in `payment`"New value: +"'otp': this booking is confirmed with a 6-digit code; delivered and not_sent_reason say whether one went on this call. 'payment': no code — this booking is confirmed by paying the deposit in `payment`"
    • changedOutput schema / properties / confirmation / properties / not_sent_reason / description
      Previous value: -"Present when this call could not confirm a send. 'daily_limit': a daily messaging limit was reached, so no code went. 'not_sent': no code was sent and none will arrive, because nothing could send it to this contact. 'unavailable': a send was attempted and its outcome is unknown, so a code may still arrive. Tell the customer which it is, and offer the business's other contact"New value: +"With method 'otp', present when this call could not confirm that a code went; absent on an idempotent replay, which sends nothing. 'daily_limit': a daily messaging limit was reached, so no code went. 'not_sent': no code was sent and none will arrive, because nothing could send it to this contact. 'unavailable': a send was attempted and its outcome is unknown, so a code may still arrive. Tell the customer which it is, and offer the business's other contact"
  4. Changed3 schema fields changed
    • changedOutput schema / properties / confirmation / properties / delivered / description
      Previous value: -"False means the hold exists but no code reached the customer — the booking cannot be confirmed until one does"New value: +"False means nothing confirmed that a code went on this call, and the booking cannot be confirmed until one reaches the customer. On an idempotent replay it is always false, because a replay sends nothing: the first call's answer stands"
    • addedOutput schema / properties / confirmation / properties / not_sent_reason
      Added value: +{
      +  "description": "Present when this call could not confirm a send. 'daily_limit': a daily messaging limit was reached, so no code went. 'not_sent': no code was sent and none will arrive, because nothing could send it to this contact. 'unavailable': a send was attempted and its outcome is unknown, so a code may still arrive. Tell the customer which it is, and offer the business's other contact",
      +  "enum": [
      +    "daily_limit",
      +    "not_sent",
      +    "unavailable"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / confirmation / properties / retry_after
      Added value: +{
      +  "description": "ISO-8601 UTC, with daily_limit only. Daily send budgets reset at this time. A new reservation may retry then, subject to current budgets and delivery availability",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • addedOutput schema / properties / booking_authorization
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Present this summary and booking_details to the customer and obtain explicit agreement before passing its reference to confirm_booking.",
      +  "properties": {
      +    "consent_version": {
      +      "const": "calendar-booking-v2",
      +      "type": "string"
      +    },
      +    "notifications": {
      +      "type": "string"
      +    },
      +    "reference": {
      +      "format": "uuid",
      +      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "reference",
      +    "consent_version",
      +    "notifications"
      +  ],
      +  "type": "object"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / customer_contact / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  7. Changed3 schema fields changed
    • changedOutput schema / properties / confirmation / properties / method / description
      Previous value: -"Always 'otp' today"New value: +"'otp': a 6-digit code was sent to the customer. 'payment': no code — this booking is confirmed by paying the deposit in `payment`"
    • changedOutput schema / properties / expires_at / description
      Previous value: -"ISO-8601. When this hold lapses if the code is not confirmed"New value: +"ISO-8601. When this hold lapses if it is not confirmed (by code, or by payment when payment.required)"
    • addedOutput schema / properties / payment
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Always present. required:false — confirm with the code (confirmation.method 'otp'). required:true — the customer pays amount_cents (currency) to confirm; balance_due_cents is paid at the visit.",
      +  "properties": {
      +    "amount_cents": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "balance_due_cents": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "currency": {
      +      "type": "string"
      +    },
      +    "kind": {
      +      "enum": [
      +        "deposit",
      +        "full"
      +      ],
      +      "type": "string"
      +    },
      +    "required": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "required"
      +  ],
      +  "type": "object"
      +}
  8. Changed1 schema field changed
    • addedOutput schema / properties / booking_details
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "For configured calendars: present these fixed booking details to the customer before confirming their code. No owner approval is required.",
      +  "properties": {
      +    "business_name": {
      +      "type": "string"
      +    },
      +    "calendar_name": {
      +      "type": "string"
      +    },
      +    "end": {
      +      "type": "string"
      +    },
      +    "reference": {
      +      "type": "string"
      +    },
      +    "start": {
      +      "type": "string"
      +    },
      +    "timezone": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "business_name",
      +    "timezone",
      +    "start",
      +    "end",
      +    "calendar_name",
      +    "reference"
      +  ],
      +  "type": "object"
      +}
  9. Changed3 schema fields changed
    • addedInput schema / properties / customer_contact / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "email"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "phone"
      +    ]
      +  }
      +]
    • changedInput schema / properties / window_end / description
      Previous value: -"Slot end (Unix seconds)"New value: +"Slot end (Unix seconds, an absolute instant) — the matching get_availability slot's `end`; see window_start."
    • changedInput schema / properties / window_start / description
      Previous value: -"Slot start (Unix seconds)"New value: +"Slot start (Unix seconds, an absolute instant). Take it from a get_availability slot: that response carries the business's `timezone`, so request a wide availability window there and filter the returned slots locally rather than guessing the zone."
  10. Changed1 schema field changed
    • changedInput schema / properties / customer_contact / properties / phone / description
      Previous value: -"SMS fallback for the confirmation code when no email is given. Give it in E.164 form, e.g. +15125551234; a bare national number is accepted and read as US. If it cannot be resolved to a real number and no email was supplied, the call returns invalid_phone rather than holding a slot nobody can confirm."New value: +"SMS fallback for the confirmation code when no email is given. Any common way of writing a number is accepted and reformatted for you: (512) 317-1992, 512-317-1992 and 5123171992 all work, and a bare national number is read as US. Only input that cannot be read as a number at all is refused, and then only when no email was supplied, since a hold nobody can confirm is worse than a refused call."
  11. Changed1 schema field changed
    • changedInput schema / properties / customer_contact / properties / phone / description
      Previous value: -"SMS fallback for the confirmation code when no email is given"New value: +"SMS fallback for the confirmation code when no email is given. Give it in E.164 form, e.g. +15125551234; a bare national number is accepted and read as US. If it cannot be resolved to a real number and no email was supplied, the call returns invalid_phone rather than holding a slot nobody can confirm."
  12. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "confirmation": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "channel": {
      +          "description": "Where the code went: 'email', 'sms', or 'none' if delivery was unavailable",
      +          "type": "string"
      +        },
      +        "delivered": {
      +          "description": "False means the hold exists but no code reached the customer — the booking cannot be confirmed until one does",
      +          "type": "boolean"
      +        },
      +        "method": {
      +          "description": "Always 'otp' today",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "method",
      +        "channel",
      +        "delivered"
      +      ],
      +      "type": "object"
      +    },
      +    "expires_at": {
      +      "description": "ISO-8601. When this hold lapses if the code is not confirmed",
      +      "type": "string"
      +    },
      +    "idempotent_replay": {
      +      "description": "Present and true when this idempotency_key already had a reservation; no new code was sent",
      +      "type": "boolean"
      +    },
      +    "reservation_id": {
      +      "format": "uuid",
      +      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Reservation state — 'pending_offer' on a fresh hold; a replay returns the existing row's state",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "reservation_id",
      +    "status",
      +    "expires_at",
      +    "confirmation"
      +  ],
      +  "type": "object"
      +}
  13. Changed4 schema fields changed
    • changedInput schema / properties / customer_contact / description
      Previous value: -"Customer contact information"New value: +"How to reach the customer. MUST include at least one of email or phone — the confirmation code is delivered there, and a hold nobody can confirm is unreachable from both sides. Email is used when both are present."
    • addedInput schema / properties / customer_contact / properties / email / description
      Added value: +"Where the 6-digit confirmation code is sent, preferred over phone"
    • addedInput schema / properties / customer_contact / properties / name / description
      Added value: +"Customer's name, if known"
    • addedInput schema / properties / customer_contact / properties / phone / description
      Added value: +"SMS fallback for the confirmation code when no email is given"
  14. Changed1 schema field changed
    • addedInput schema / properties / offer_id
      Added value: +{
      +  "description": "Optional id of a signed get_quote offer to redeem against this reservation. Omit for a business with no exact-priced service — authentication is a capability upgrade here, never a toll.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
  15. Changed2 schema fields changed
    • addedInput schema / properties / customer_contact / properties / email / format
      Added value: +"email"
    • addedInput schema / properties / customer_contact / properties / email / pattern
      Added value: +"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  16. Changed10 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / agent_id / description
      Added value: +"Optional agent identifier"
    • removedInput schema / properties / customer_contact / additionalProperties
      Removed value: -false
    • addedInput schema / properties / customer_contact / description
      Added value: +"Customer contact information"
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Unique key for idempotent reservation"
    • addedInput schema / properties / slug / description
      Added value: +"Business slug identifier"
    • addedInput schema / properties / window_end / description
      Added value: +"Slot end (Unix seconds)"
    • addedInput schema / properties / window_end / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / window_start / description
      Added value: +"Slot start (Unix seconds)"
    • addedInput schema / properties / window_start / maximum
      Added value: +9007199254740991
  17. Changed10 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / agent_id / description
      Removed value: -"Optional agent identifier"
    • addedInput schema / properties / customer_contact / additionalProperties
      Added value: +false
    • removedInput schema / properties / customer_contact / description
      Removed value: -"Customer contact information"
    • removedInput schema / properties / idempotency_key / description
      Removed value: -"Unique key for idempotent reservation"
    • removedInput schema / properties / slug / description
      Removed value: -"Business slug identifier"
    • removedInput schema / properties / window_end / description
      Removed value: -"Slot end (Unix seconds)"
    • removedInput schema / properties / window_end / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / window_start / description
      Removed value: -"Slot start (Unix seconds)"
    • removedInput schema / properties / window_start / maximum
      Removed value: -9007199254740991
  18. Changed10 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / agent_id / description
      Added value: +"Optional agent identifier"
    • removedInput schema / properties / customer_contact / additionalProperties
      Removed value: -false
    • addedInput schema / properties / customer_contact / description
      Added value: +"Customer contact information"
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Unique key for idempotent reservation"
    • addedInput schema / properties / slug / description
      Added value: +"Business slug identifier"
    • addedInput schema / properties / window_end / description
      Added value: +"Slot end (Unix seconds)"
    • addedInput schema / properties / window_end / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / window_start / description
      Added value: +"Slot start (Unix seconds)"
    • addedInput schema / properties / window_start / maximum
      Added value: +9007199254740991
  19. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description backs both with concrete behavior: re-using idempotency_key returns the original reservation and sends no code, and the hold lapses after 15 minutes. It also discloses delivery-failure semantics (confirmation.delivered=false plus not_sent_reason) that annotations cannot express. It stops short of stating what destructive effect a reservation has on the calendar or what permissions/credentials are needed.

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 core action and outcome, then branches into idempotency, delivery failure, and the deposit path in a logical order. It is dense but each sentence carries distinct operational information; only a light trim would be possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, nested-object mutation with an output schema, the description covers the preconditions (offer_id path), the lifecycle (pending for 15 minutes), retry behavior, degraded delivery, and an agent obligation on customer_notice. An agent has everything needed to invoke it correctly and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies; the description earns above that by explaining offer_id's origin and its consequence (quote_required, no code sent, payment block returned instead), which is operational meaning the schema does not carry. Slug, window bounds, and customer_contact are left entirely to their already-detailed schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Reserve a time slot on an active configured calendar') and immediately characterizes the outcome as a 'pending_offer reservation', which separates it from confirm_booking-style terminal actions without needing the sibling's schema. The 15-minute expiry and code-send behavior further pin down exactly what this call does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit conditional routing: at a business that takes a deposit for agent bookings, pass offer_id from get_quote, otherwise the result is quote_required. It also names the source of the required time window (get_availability slots) in the schema and tells the agent to display customer_notice verbatim, so the agent knows both when to call and what to do with the answer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources