Crawlora MCP

datasets_apple_maps_places_nearby

Read-only

Find stored Apple Maps places within a radius of a coordinate, nearest first, with the distance in meters on every item. Requires lat, lon and radius_m, and pages through the stored directory rather than the live 25-place Apple search. Costs 1 credit per record returned (minimum 2), so keep page_size to what you need.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>",
      "radius_m": "<radius_m>"
    },
    "name": "datasets_apple_maps_places_nearby"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Required center latitude, from -90 through 90.
`lon`	Yes	Required center longitude, from -180 through 180.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`category`	No	Optional exact Apple category name, max 128 characters.
`radius_m`	Yes	Required search radius in meters, from 1 through 50000.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`min_rating`	No	Optional minimum rating, from 0 through 5. Unrated places are excluded by any value above 0.
`min_rating_count`	No	Optional minimum number of ratings behind the rating, 0 or greater.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses ordering (nearest first), that distance is attached to every item, that results come from a paged stored directory, and a concrete cost model (1 credit per record, minimum 2) with advice to size page_size accordingly. That is exactly the kind of rate/cost context annotations cannot carry.

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 sentences, no filler. The identifying behavior (stored places, radius, nearest first, distances) comes first and the cost caveat comes last as an actionable constraint.

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?

An output schema exists, so return values need not be explained, yet the description still flags that each item carries a distance in meters. Combined with the source-of-data distinction, pagination note and cost model, an agent has everything needed to call it correctly against an 8-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 meaning on top by tying page_size to billing (credits per returned record), which the schema only describes as a max-100 page size. It also restates the required trio, but does not explain radius/category/filter interactions beyond the schema.

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 gives a specific verb (find), resource (stored Apple Maps places), scope (within a radius of a coordinate), ordering (nearest first) and output detail (distance in meters on every item). It distinguishes the source from the live Apple search, though it never names the concrete sibling (datasets_apple_maps_places_search) that would let an agent route without inferring.

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?

It establishes context for choosing this tool — stored directory rather than the live 25-place Apple search — and adds actionable guidance to keep page_size small because of per-record credit cost. It stops short of explicitly naming the alternative tool for keyword-based lookups or stating when-not to use this one.

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

All Crawlora MCP 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.

Resources

Need Help?