Skip to main content
Glama

Find businesses

find_businesses
Read-onlyIdempotent

Use this when a person wants to book or ask about something on Bookatu and has no business in mind yet. Give the country and at least one of service, name or place (a town, city or area the person named, never their own position). Returns up to 10 businesses that chose to be found here, in name order, each with its city and area (never a street address), the languages it speaks, its lowest price, the services that match and its booking page. bookVia says how the business and each service are reached: assistant, website or enquiry, and a trip also has days. At a business whose bookVia is enquiry nothing is booked: the person asks it with send_enquiry. No business pays to be listed or placed. Do not use for a business you already know: pass it to get_business.

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": {
      "country": "<country>"
    },
    "name": "find_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe business's name, or part of it.
limitNo1 to 10, 10 when not given.
placeNoA town, city or area the person named. Never their own position.
cursorNoThe nextCursor of the answer before, for the next page.
speaksNoA language the business should speak with the client (BCP 47).
countryYesThe country to look in, ISO 3166-1 alpha-2, such as NZ.
serviceNoWhat the person wants done, in their words. Matched against service names, categories and descriptions.
languageNoThe language to answer in (BCP 47).
clientTimeZoneNoThe client's IANA time zone, such as America/Toronto. Ask for their city when unsure.

Output Schema

NameRequiredDescriptionDefault
metaYes
noteYesResults are not ads: no business pays for where it appears.
businessesYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / businesses / items / properties / bookVia
      Added value: +{
      +  "description": "assistant: a time can be held here. website: the client books on the business's booking page. enquiry: the business takes enquiries only, so the person asks it with send_enquiry and nothing is booked.",
      +  "enum": [
      +    "assistant",
      +    "website",
      +    "enquiry"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / businesses / items / properties / matchedServices / items / properties / bookVia
      Added value: +{
      +  "description": "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.",
      +  "enum": [
      +    "assistant",
      +    "website",
      +    "enquiry"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / businesses / items / properties / matchedServices / items / properties / days
      Added value: +{
      +  "description": "A trip's length in whole days.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedOutput schema / properties / businesses / items / properties / matchedServices / items / required
      Previous value: -[
      -  "serviceId",
      -  "name",
      -  "price",
      -  "durationMin"
      -]New value: +[
      +  "serviceId",
      +  "name",
      +  "price",
      +  "durationMin",
      +  "bookVia"
      +]
    • changedOutput schema / properties / businesses / items / required
      Previous value: -[
      -  "business",
      -  "name",
      -  "kind",
      -  "city",
      -  "country",
      -  "timeZone",
      -  "speaks",
      -  "priceFrom",
      -  "matchedServices",
      -  "bookingPageUrl"
      -]New value: +[
      +  "business",
      +  "name",
      +  "kind",
      +  "city",
      +  "country",
      +  "timeZone",
      +  "speaks",
      +  "priceFrom",
      +  "matchedServices",
      +  "bookingPageUrl",
      +  "bookVia"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: a cap of 10 results, name ordering, city/area only (never street address), the bookVia reach modes (assistant/website/enquiry), and that listing is not paid placement. That is real added context, though it stops short of pagination/cursor behavior guidance.

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-loads the trigger condition before the mechanics, which is the right ordering. It is dense but nearly every clause carries information; the only weakness is that the long middle sentences about return shape and bookVia run together and could be broken up for faster scanning.

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?

Complete for a filtered discovery tool: trigger, required and optional inputs, result cap, ordering, dropped detail (no street address), and the booking-path semantics are all present. An output schema also exists, so return values are doubly covered.

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 description coverage is 100%, so the baseline is 3. The description earns above that by explaining the combination rule ('Give the country and at least one of service, name or place') and by reinforcing the place constraint ('never their own position'), which tells the agent how parameters interact rather than just what each one is.

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 pair (find businesses on Bookatu) plus the precise scope: the person 'has no business in mind yet'. It also distinguishes itself from the sibling get_business by name, so an agent can route correctly without opening either 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 trigger ('when a person wants to book or ask about something... and has no business in mind yet'), an explicit exclusion with the alternative ('Do not use for a business you already know: pass it to get_business'), and a follow-on path for enquiry-only results (send_enquiry). Nothing is left to inference.

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