Skip to main content
Glama

get_booking_availability

Read-onlyIdempotent

List online appointment times on a business-local date. Use serviceIds for services booked back to back. Slot start times are Unix milliseconds. Some onsite services require an address on the booking page.

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": {
      "date": "<date>"
    },
    "name": "get_booking_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
serviceIdNo
locationIdNo
serviceIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety needs no restating. The description adds genuinely new behavior: results are keyed to a business-local date, slot start times are Unix milliseconds, and some onsite services require an address on the booking page – all useful for interpreting results and pre-empting booking failures.

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?

Four short sentences, front-loaded with the core purpose, then progressively narrower operational details. No redundant wording; the address caveat is the only sentence bordering on tangential.

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?

No output schema exists, and the description compensates by specifying the slot time format (Unix milliseconds). Adequate for a read-only availability query, though the unexplained distinction between the singular serviceId and the serviceIds array leaves a small gap.

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 0% across four parameters, so the description must carry the load and only partly does. It explains serviceIds (back-to-back services) and implies the date is business-local, but says nothing about serviceId vs serviceIds precedence or what locationId controls.

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: listing online appointment times scoped to a business-local date. It does not explicitly distinguish itself from siblings, but no sibling in the catalog appears to return availability, so the purpose is unambiguous on its own terms.

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?

Provides one concrete usage rule – use serviceIds when services must be booked back to back – but gives no when-to-use/when-not guidance relative to alternatives and no statement of prerequisites (e.g. whether a location or service must be resolved first). Usage is implied rather than framed.

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