Skip to main content
Glama

Open times

check_availability
Read-onlyIdempotent

Use this when the person has chosen a service and wants to know when it can be done. Returns open times over up to 14 days, each on the business's clock and, when you pass clientTimeZone, on the person's clock too, with the price at that time. A time marked bookVia assistant has a slotId to pass to hold_booking within 30 minutes. Quote times from the display fields as given. A service whose bookVia is enquiry has no times here. Do not use for holding or booking a time: only hold_booking holds one.

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": {
      "business": "<business>",
      "serviceId": "<serviceId>",
      "dateFrom": "<dateFrom>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1 to 40, 12 when not given.
dateToNoYYYY-MM-DD, at most 14 days in all.
staffIdNoA person, when the client wants one.
addOnIdsNo
businessYesThe business: its bookatu.com link or its own domain on Bookatu, or its slug.
dateFromYesYYYY-MM-DD.
languageNoThe language to answer in (BCP 47).
dateClockNoWhose calendar the dates are on (the business's when not given).
partOfDayNo
partySizeNo
serviceIdYes
locationIdNoA branch of the business.
clientTimeZoneNoThe client's IANA time zone, such as America/Toronto. Ask for their city when unsure.

Output Schema

NameRequiredDescriptionDefault
daysYes
metaYes
moreYes
notesYes
slotsYes
clientYes
windowYes
bookViaYesassistant: a time can be held here. website: the client books on the business's booking page. enquiry: the person asks the business with send_enquiry.
serviceYes
businessYes
warningsYes
bookingPageUrlNoWhere the client books a time marked website.
freeCancellationRuleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / business / description
      Previous value: -"The business: its Bookatu name (slug), a bookatu.com link to it, or its own website address."New value: +"The business: its bookatu.com link or its own domain on Bookatu, or its slug."
    • changedOutput schema / properties / bookVia / description
      Previous value: -"assistant: a time can be held here. website: the client books on the business's booking page."New value: +"assistant: a time can be held here. website: the client books on the business's booking page. enquiry: the person asks the business with send_enquiry."
    • changedOutput schema / properties / bookVia / enum
      Previous value: -[
      -  "assistant",
      -  "website"
      -]New value: +[
      +  "assistant",
      +  "website",
      +  "enquiry"
      +]
    • changedOutput schema / properties / slots / items / properties / bookVia / description
      Previous value: -"assistant: a time can be held here. website: the client books on the business's booking page."New value: +"assistant: a time can be held here. website: the client books on the business's booking page. enquiry: the person asks the business with send_enquiry."
    • changedOutput schema / properties / slots / items / properties / bookVia / enum
      Previous value: -[
      -  "assistant",
      -  "website"
      -]New value: +[
      +  "assistant",
      +  "website",
      +  "enquiry"
      +]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the 14-day result window, the dual-timezone behavior when clientTimeZone is passed, that prices accompany each time, the meaning of bookVia=assistant (slotId must reach hold_booking within 30 minutes), the bookVia=enquiry dead end, and the instruction to quote display fields verbatim. These are non-obvious operational facts an agent could not derive from annotations.

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?

Front-loaded with the use condition, then output shape, then the assistant/enquiry exceptions, then the anti-pattern. Every sentence carries a distinct constraint; nothing restates the title or annotations.

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 13-parameter read tool with an output schema, the description covers the decisions an agent must make: when to call, what comes back, which returned field to use, the time limit on the slotId, and which sibling to route to for mutation. Return-value explanation is not required given the output schema, and it does not over-explain.

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 69%, so the schema carries much of the load, but the description adds genuine meaning not in the schema: clientTimeZone changes which clock returned times are rendered on, and the 14-day horizon constrains dateFrom/dateTo. It does not add prose meaning for staffId, partySize, partOfDay, or addOnIds, leaving those to the schema.

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 — returns open times for a chosen service — and scopes the trigger condition ('when the person has chosen a service and wants to know when it can be done'). It explicitly separates itself from hold_booking and from enquiry-type services, so an agent can distinguish it from siblings without opening any schema.

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 an explicit when-to-use condition, an explicit when-not-to-use clause ('Do not use for holding or booking a time'), and names the correct alternative (hold_booking). It also covers a notable edge case: services whose bookVia is enquiry return no times here, which prevents a wasted or misinterpreted call.

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