Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_google_map_businesses_nearby

Search stored Google Maps businesses near a coordinate, filtered by radius, category, rating, and review count.

Instructions

Search nearby stored Google Maps businesses. Searches stored Google Maps businesses near a coordinate in dataset id enum value google-map-businesses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
radius_mYesRadius in meters, max 50000
categoryNoExact category filter, max 128 characters
min_ratingNoMinimum rating, 0 through 5
min_review_countNoMinimum review count
pageNoPage number, defaults to 1
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
Behavior2/5

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

No annotations present, and description adds minimal behavioral info beyond the schema. Does not disclose read-only nature, pagination behavior, or any side effects. Context of 'stored' is helpful but insufficient.

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

Conciseness5/5

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

Two concise sentences, no redundant or irrelevant information. Essential details front-loaded.

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?

Lacks output schema, so description could explain result format or behavior. Mentions dataset id but not that it's an enum. Overall adequate but not thorough.

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 all parameters are documented in schema. Description adds context about dataset id but does not enhance parameter meaning beyond 'near a coordinate'.

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?

Describes tool as searching nearby stored Google Maps businesses, with specific spatial filtering by coordinate. Clearly distinguishes from sibling tools like datasets_google_map_businesses_search and datasets_google_map_businesses_item.

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?

Implies usage for spatial searching within a stored dataset, but does not explicitly differentiate from similar tools like datasets_google_map_businesses_search or provide when-not-to-use scenarios.

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