Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_apple_maps_places_nearby

Find stored Apple Maps places within a radius of given coordinates, nearest first, with pagination and distance per item. Use it to explore observed nearby places without triggering live scraping.

Instructions

Find nearby stored Apple Maps places. Returns stored Apple Maps places within a radius of a point, nearest first, from dataset id apple-maps-places. lat, lon and radius_m are required. Unlike the live apple-maps-search endpoint (which returns at most 25 places per call), this pages through the stored directory with distance_m on every item. Coverage is observed, not complete. Does not trigger live scraping. Billing: this endpoint costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
latYesCenter latitude, from -90 through 90
lonYesCenter longitude, from -180 through 180
pageNoPage number, defaults to 1
categoryNoExact Apple category name
radius_mYesSearch radius in meters, 1 through 50000
page_sizeNoPage size, defaults to 20 and maxes at 100
min_ratingNoMinimum rating, from 0 through 5
min_rating_countNoMinimum number of ratings behind the rating

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses billing (1 credit per record, minimum 2), that coverage is observed and not complete, that it does not trigger live scraping, that results are nearest-first with distance_m, and that it pages through the directory.

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?

Front-loads the core purpose, then layers in the live-endpoint comparison, coverage caveat, and billing details without wasted words. Every sentence adds relevant decision or operational information.

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

Completeness5/5

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

Given no output schema and no annotations, the description supplies the key missing context: return ordering, distance_m on each item, coverage caveat, billing cost, paging behavior, and the distinction from the live endpoint. An agent has enough to call it correctly and understand the cost/coverage trade-off.

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 eight parameters including required lat/lon/radius_m, page, page_size, category, and rating filters. The description adds no parameter-level meaning beyond restating which fields are required, so the baseline of 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?

States a specific verb and resource ('Find nearby stored Apple Maps places') and scopes it to the stored dataset 'apple-maps-places'. It explicitly distinguishes itself from the live 'apple-maps-search' endpoint and implies differentiation from other Apple Maps dataset siblings by emphasizing stored coverage.

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

Usage Guidelines4/5

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

Names the live 'apple-maps-search' alternative and explains the key difference: live returns at most 25 per call while this pages through the stored directory. That gives a clear selection rationale, though it does not explicitly state when this tool should not be used.

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

Deploy Server

Other Tools