Skip to main content
Glama
BACH-AI-Tools

Local Business Data MCP Server

search_in_area

Search for businesses within a specific geographic area using coordinates and zoom level to define the search boundary.

Instructions

Search businesses in a specific geographic area defined by a center coordinate point and zoom level. To see it in action, make a query on Google Maps, wait for the results to show, move the map or change the zoom and click \

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query / keyword
latYesLatitude of the center coordinate point of the area to search in.37.359428
lngYesLongitude of the center coordinate point of the area to search in.-121.925337
zoomYesZoom level on which to make the search (the search area / viewport is determined by lat, lng and zoom on a 1000x1000 screen).
limitNoMaximum number of businesses to return. Default: 20 Allowed values: 1-50020
languageNoSet the language of the results. For a list of supported language codes see https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes . Default: en
regionNoQuery Google Maps from a particular region or country. For a list of supported region/country codes see https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes (Alpha-2 code). Default: us
subtypesNoFind businesses with specific subtypes, specified as a comma separated list of types (business categories). For the complete list of types, see https://daltonluka.com/blog/google-my-business-categories. Examples: Plumber,Carpenter,Electrician Night club,Dance club,Bar,Pub
extract_emails_and_contactsNoExample value:
fieldsNoA comma separated list of business fields to include in the response (field projection). By default all fields are returned. Example: business_id,type,phone_number,full_address
X-User-AgentNoDevice type for the search. Default desktop.
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the geographic area definition but doesn't cover important aspects like rate limits, authentication requirements, pagination behavior, error conditions, or what happens when no results are found. The Google Maps reference is confusing rather than clarifying.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is clear and front-loaded, but the second sentence about Google Maps is confusing and doesn't add value for an AI agent. The description could be more concise by removing the instructional content and focusing purely on tool functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 11 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how results are structured, error handling, or performance characteristics. The Google Maps reference creates confusion rather than providing helpful context.

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 11 parameters thoroughly. The description adds minimal value beyond what's in the schema - it mentions center coordinate and zoom level (which are already well-described in the schema) but doesn't provide additional context about parameter interactions or usage patterns.

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?

The description clearly states the tool searches for businesses in a specific geographic area defined by coordinates and zoom level. It specifies the resource (businesses) and geographic scope, but doesn't explicitly differentiate from sibling tools like 'search' or 'search_nearby' beyond mentioning the area definition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'search', 'search_nearby', or 'bulk_search'. The second sentence about Google Maps is instructional rather than providing usage context. There's no mention of prerequisites, limitations, or comparative advantages.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-local-business-data'

If you have feedback or need assistance with the MCP directory API, please join our Discord server