Skip to main content
Glama

Business details and policies

get_business
Read-onlyIdempotent

Use this when a person wants to book with a business on Bookatu and you need its details first. Give the business as its bookatu.com link or its own domain on Bookatu, or as its slug. Returns its city and area (never a street address), its time zone and the time there now, this week's opening hours, its branches, its booking policies, whether a time can be held here and whether it takes enquiries through assistants. Do not use for searching for a business by place or by what it offers.

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>"
    },
    "name": "get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessYesThe business: its bookatu.com link or its own domain on Bookatu, or its slug.
languageNoThe language to answer in (BCP 47).
locationIdNoA branch of the business.
clientTimeZoneNoThe client's IANA time zone, such as America/Toronto. Ask for their city when unsure.

Output Schema

NameRequiredDescriptionDefault
nowYes
areaNo
cityYes
kindYesWhat kind of business it is.
metaYes
nameYes
slugYes
phoneNoThe business's own phone, only when it shows it to clients.
clientYes
speaksYes
countryYesISO 3166-1 alpha-2.
branchesYes
currencyYes
policiesYes
timeZoneYes
agentBookingYes
hoursThisWeekYes
bookingPageUrlYes
storefrontLanguageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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."
    • addedOutput schema / properties / agentBooking / properties / enquiries
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / agentBooking / required
      Previous value: -[
      -  "available",
      -  "depositsInChat"
      -]New value: +[
      +  "available",
      +  "enquiries",
      +  "depositsInChat"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful domain context beyond that, including that city and area are returned but never a street address, plus current time, opening hours, policies, hold availability, and assistant enquiry support. It does not discuss error or not-found behavior, so it falls short of a 5.

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 three sentences and front-loads the use case, then input formats, then a compact return list and exclusion. There is no filler, and the return list is relevant to a details-and-policies tool.

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?

The tool is read-only and has an output schema, so the description need not document every return field. It still covers the trigger, accepted identifiers, key privacy constraint, returned domain data, and a relevant exclusion, which is enough for correct invocation.

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 all four parameters. The description restates the accepted business identifier formats but adds no meaning for language, locationId, or clientTimeZone beyond what the schema provides. This matches the baseline of 3 when the schema does the heavy lifting.

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?

The description states a specific resource and task: retrieving a business's details before booking. It lists the returned domain data and explicitly distinguishes the tool from searching by place or offering, which separates it from find_businesses and other booking siblings.

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?

It gives a clear trigger: use when a person wants to book and needs the business's details first. It also gives an explicit exclusion for searching by place or by what the business offers, which functionally routes discovery requests elsewhere.

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