Appointment Booking

find_business

Read-onlyIdempotent

Find real businesses near a place, sorted by distance (nearest of those examined; see result.search). Data: OpenStreetMap (ODbL, (c) OSM contributors); phone, website, hours only when mapped. Coverage varies; community-mapped, NOT verified by us; source=openstreetmap rows cannot be booked. Answers within about 5 s: status partial (search_in_progress) means repeat the call. If OSM is down: retriable 'temporarily unavailable', never invented rows. [free, no key] [beta]

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Instead of location: a city, e.g. 'Muscat, Oman'.
`region`	No	With city: a state or region.
`location`	Yes	City/town or ZIP, optionally with country ('Nizwa, Oman'). Geocoded by OSM.
`vertical`	No
`capability`	No	Kind of business: 'dentist', 'cafe', 'plumber'. Use it or vertical.
`price_band`	No	Supply-network rows only (OpenStreetMap has no prices).
`max_results`	No
`availability_window`	No	Accepted but NOT APPLIED: it does not narrow results (no live calendars). The…

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 3, 2026

changedInput schema / properties / availability_window / description

Previous value: -"Accepted but NOT APPLIED - it does not narrow results. We do not hold live…"New value: +"Accepted but NOT APPLIED: it does not narrow results (no live calendars). The…"

changedInput schema / properties / capability / description

Previous value: -"Kind of business, e.g. 'haircut', 'plumber', 'dentist'. Mapped to OSM tags."New value: +"Kind of business: 'dentist', 'cafe', 'plumber'. Use it or vertical."

changedInput schema / properties / city / description

Previous value: -"Alternative to location: a top-level city, normalised into…"New value: +"Instead of location: a city, e.g. 'Muscat, Oman'."

changedInput schema / properties / location / properties / zip_or_city / description

Previous value: -"City, town, address or postal code, optionally with the country, e.g. 'Nizwa, Oman'. A bare 5-digit ZIP is read as a US ZIP; give any non-US postal code with its country (e.g. '10115, Germany')."New value: +"Town, city, address or postal code, with the country if not US: 'Nizwa, Oman'. A bare 5-digit ZIP is a US ZIP; add the country for any other postal code."

changedInput schema / properties / price_band / description

Previous value: -"Supply-network rows only; OpenStreetMap has no prices."New value: +"Supply-network rows only (OpenStreetMap has no prices)."

changedInput schema / properties / region / description

Previous value: -"Alternative to location: a top-level state/region, normalised into…"New value: +"With city: a state or region."

changedInput schema / required

Previous value: -[
-  "vertical",
-  "location"
-]New value: +[
+  "location"
+]

Changed5 schema fields changedSep 30, 2026

changedInput schema / properties / capability / description

Previous value: -"Specific service capability required, e.g. 'haircut', 'plumbing',…"New value: +"Kind of business, e.g. 'haircut', 'plumber', 'dentist'. Mapped to OSM tags."

changedInput schema / properties / location / description

Previous value: -"Where to search. Matched against the business's city, state and ZIP as text -…"New value: +"City/town or ZIP, optionally with country ('Nizwa, Oman'). Geocoded by OSM."

changedInput schema / properties / location / properties / radius_miles / description

Previous value: -"Accepted but NOT applied - no coordinates exist, so results are not restricted to this radius. Disclosed back as radius_miles_applied: false."New value: +"Radius in miles (default 3.1, max 25); applies to OpenStreetMap results only."

addedInput schema / properties / location / properties / zip_or_city / description

Added value: +"City, town, address or postal code, optionally with the country, e.g. 'Nizwa, Oman'. A bare 5-digit ZIP is read as a US ZIP; give any non-US postal code with its country (e.g. '10115, Germany')."

addedInput schema / properties / price_band / description

Added value: +"Supply-network rows only; OpenStreetMap has no prices."

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / city

Added value: +{
+  "description": "Alternative to location: a top-level city, normalised into…",
+  "type": "string"
+}

addedInput schema / properties / region

Added value: +{
+  "description": "Alternative to location: a top-level state/region, normalised into…",
+  "type": "string"
+}

Changed2 schema fields changedSep 22, 2026

removedInput schema / properties / city

Removed value: -{
-  "description": "Alternative to location: a top-level city, normalised into…",
-  "type": "string"
-}

removedInput schema / properties / region

Removed value: -{
-  "description": "Alternative to location: a top-level state/region, normalised into…",
-  "type": "string"
-}

Changed1 schema field changedSep 22, 2026

changedInput schema / properties / location / properties / radius_miles / description

Previous value: -"Accepted but NOT applied. The supply directory holds no coordinates, so no distance filter can be honoured; results are not restricted to this radius. Sending it is recorded and disclosed back as radius_miles_applied: false."New value: +"Accepted but NOT applied - no coordinates exist, so results are not restricted to this radius. Disclosed back as radius_miles_applied: false."

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / location / properties / radius_miles / description

Added value: +"Accepted but NOT applied. The supply directory holds no coordinates, so no distance filter can be honoured; results are not restricted to this radius. Sending it is recorded and disclosed back as radius_miles_applied: false."

Changed6 schema fields changedSep 22, 2026

addedInput schema / properties / city

Added value: +{
+  "description": "Alternative to location: a top-level city, normalised into…",
+  "type": "string"
+}

addedInput schema / properties / location / description

Added value: +"Where to search. Matched against the business's city, state and ZIP as text -…"

removedInput schema / properties / location / properties / radius_miles / default
```
Removed value: -10
```
addedInput schema / properties / location / properties / radius_miles / minimum
```
Added value: +0
```
addedInput schema / properties / max_results / minimum
```
Added value: +1
```

addedInput schema / properties / region

Added value: +{
+  "description": "Alternative to location: a top-level state/region, normalised into…",
+  "type": "string"
+}

Changed1 schema field changedSep 21, 2026
- removedInput schema / properties / vertical / description
```
Removed value: -"Service vertical to search within"
```

Changed2 schema fields changedSep 10, 2026

changedInput schema / properties / availability_window / description

Previous value: -"Accepted but NOT APPLIED - it does not narrow results. We do not hold live calendars for the supply network. The response carries availability_window_applied: false when you send one. To book a specific slot use schedule_appointment with requested_time, which checks real availability."New value: +"Accepted but NOT APPLIED - it does not narrow results. We do not hold live…"

changedInput schema / properties / capability / description

Previous value: -"Specific service capability required, e.g. 'haircut', 'plumbing', 'tax_consultation'"New value: +"Specific service capability required, e.g. 'haircut', 'plumbing',…"

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses ~5s latency, that partial/search_in_progress means the call must be repeated, that an OSM outage yields a retriable 'temporarily unavailable' rather than fabricated rows, and that results are community-mapped and NOT verified by the provider. These are exactly the operational traits an agent needs and none are in the annotations.

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 verb+resource, then grouped caveats (data provenance, latency/status, failure mode, tags). Dense but nearly every clause carries information; the trailing '[free, no key] [beta]' tags are slightly cluttered but useful.

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?

With 8 params, nested objects, and no output schema, the definition adequately covers provenance, retry semantics, latency, and the booking limitation, and points at result.search for ordering. It stops short of describing result fields or pagination, leaving a small gap for a discovery tool.

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 75%, so the schema already carries most parameter meaning (radius_miles default/max, price_band scope, availability_window not applied). The description adds little parameter-specific detail of its own beyond the booking constraint tied to source rows, so the baseline 3 applies.

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?

Specific verb+resource: 'Find real businesses near a place, sorted by distance', with the result ordering and the fact that sorting covers only examined rows made explicit. This cleanly separates it from siblings like verify_business, call_business, and capture_lead, which act on a business rather than discovering one.

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?

Implied context is present: it is the discovery step ('find real businesses'), and the caveat that source=openstreetmap rows cannot be booked hints at a downstream booking/verification flow. However it never explicitly states when to prefer this over siblings such as verify_business, nor does it name any alternative or exclusion condition, so usage must be inferred.

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

All Appointment Booking tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

find_business

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources