Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_google_map_nearby

Search stored Google Maps businesses near a location by latitude, longitude, and radius. Filter by category, minimum rating, and review count to find relevant results.

Instructions

Search nearby stored Google Maps businesses. Searches stored Google Maps businesses near a coordinate in dataset id enum value google-map-businesses. category is a Google Maps type token in lower-case snake_case (e.g. dentist, bus_stop, atm), both as the category filter and in each result's category field. A rating of 0 means no aggregate rating is available for that business (not a literal zero-star score); read it together with review_count, and note that min_rating above 0 excludes unrated businesses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
pageNoPage number, defaults to 1
categoryNoExact category filter: a Google Maps type token in lower-case snake_case (e.g. dentist, bus_stop), max 128 characters
radius_mYesRadius in meters, max 50000
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
min_ratingNoMinimum rating, 0 through 5. Businesses with no aggregate Google rating are returned with rating null, so any min_rating above 0 excludes them.
min_review_countNoMinimum review count
Behavior3/5

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

With no annotations, the description carries full burden. It explains the dataset id, category format, rating meaning (0 means no aggregate rating), and min_rating effect. However, it does not disclose pagination behavior, sorting, result limits, or the structure of returned data beyond category and rating. The transparency is adequate but missing important behavioral details.

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?

The description is front-loaded with the main action and consists of three sentences. It is reasonably concise, though the phrase 'Searches stored Google Maps businesses near a coordinate' is repeated from the first sentence. It could be slightly tighter but is well-organized.

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

Completeness3/5

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

The tool has 8 parameters, no output schema, and no annotations. The description covers the dataset identifier, category format, rating nuances, and min_rating effect. However, it does not describe pagination details, result ordering, or the full return structure. For a tool of this complexity, more context about output fields and result behavior is needed for completeness.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining the category token format (lower-case snake_case), rating interpretation (0 means no aggregate rating), and the effect of min_rating. It does not add beyond schema for lat, lon, radius_m, page, page_size, which are already described. The added semantics are useful but not extensive.

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 clearly states the tool's purpose: 'Search nearby stored Google Maps businesses.' It explains the specific dataset id and distinguishes from sibling tools like datasets_google_map_search and datasets_google_map_item by focusing on nearby search. The verb 'search' and resource 'stored Google Maps businesses near a coordinate' are specific.

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 implies usage for location-based searches but does not explicitly state when to use this tool versus alternatives like datasets_google_map_search or datasets_google_map_facets. It provides no when-not-to-use or explicit exclusions, leaving the agent to infer context from sibling names.

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/Crawlora-org/crawlora-mcp'

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