Agent Broker

find_business

Read-onlyIdempotent

Find real businesses near a place, sorted by distance (nearest of those examined; dense areas are narrowed, see result.search). Data: OpenStreetMap (ODbL, (c) OpenStreetMap contributors, attributed per result); phone, website, hours only when mapped. Coverage varies; community-mapped, NOT verified by us; source=openstreetmap rows cannot be booked. Plus supply-network rows. If OSM is down: retriable 'temporarily unavailable', never invented rows. [free, no key]

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Alternative to location: a top-level city, normalised into…
`region`	No	Alternative to location: a top-level state/region, normalised into…
`location`	Yes	City/town or ZIP, optionally with country ('Nizwa, Oman'). Geocoded by OSM.
`vertical`	Yes
`capability`	No	Kind of business, e.g. 'haircut', 'plumber', 'dentist'. Mapped to OSM tags.
`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. We do not hold live…

Schema Changelog

Changes observed during successful MCP inspections.

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',…"

Changed1 schema field changedAug 30, 2026

addedInput schema / properties / availability_window / description

Added 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."

First observedAug 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: data source and license attribution, that phone/website/hours exist only when mapped, that rows are community-mapped and unverified, that source=openstreetmap rows cannot be booked, and the retriable 'temporarily unavailable' failure mode with a guarantee of no invented rows.

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 purpose, and every clause carries information (license, coverage, booking restriction, failure mode). It is dense and parenthetical-heavy, making it harder to scan than it could be, but no sentence is wasted.

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 no output schema, 8 parameters and nested objects, the description covers provenance, coverage limits, failure behavior and the fact that results are unverified. It is nearly complete for an agent to call correctly, though it never explains the result shape or the 'result.search' narrowing it references.

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 documents most parameters (radius_miles defaults, availability_window not applied, price_band supply-only). The description adds little parameter-specific syntax beyond the note that dense areas are narrowed ('see result.search'), which hints at output behavior rather than clarifying an input.

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 ('Find real businesses near a place, sorted by distance') and immediately differentiates itself from verify_business by noting results are 'NOT verified by us'. An agent can distinguish it from the verification and compliance siblings without opening the schema.

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?

The description is rich in data caveats ('coverage varies', 'cannot be booked', OSM-down behavior) but never states explicitly when to call find_business versus verify_business or check_compliance. Usage context is implied by the data-provenance notes rather than given as routing guidance.

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

All Agent Broker 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