Crawlora MCP

datasets_apple_maps_places_facets

Read-only

Returns facet counts over the stored Apple Maps place directory for one field: category, country_code, state, city, price_symbol or catalog_country. Accepts the same filters as the search tool to scope the counts. Use facet=category to find the exact category names the category filter accepts.

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": {
      "facet": "<facet>"
    },
    "name": "datasets_apple_maps_places_facets"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional full-text search over place name, category, city and address; every term must match. Max 256 characters.
`lat`	No	Optional latitude for radius filtering or distance sort, from -90 through 90; supply together with lon.
`lon`	No	Optional longitude for radius filtering or distance sort, from -180 through 180; supply together with lat.
`city`	No	Optional exact city filter, max 128 characters.
`page`	No	Result page number, 1-based, default 1; page times page_size must not exceed 10000.
`sort`	No	Optional sort order. Allowed values: relevance, rating_desc, review_count_desc, updated_at_desc, distance_asc. Defaults to relevance with q, otherwise updated_at_desc.
`facet`	Yes	Required facet to aggregate. Allowed values: category, country_code, state, city, price_symbol, catalog_country.
`state`	No	Optional exact state/region filter, max 128 characters.
`category`	No	Optional exact Apple category name, max 128 characters, e.g. Coffee Shop; use facet=category to discover values.
`radius_m`	No	Optional radius in meters, from 1 through 50000; requires lat and lon.
`has_phone`	No	Optional phone presence filter; true keeps only places with a phone number.
`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. Places Apple shows no rating for have rating null; any value above 0 excludes them.
`has_website`	No	Optional website presence filter; true keeps only places with a website.
`postal_code`	No	Optional exact postal code filter, max 128 characters.
`country_code`	No	Optional ISO 3166-1 alpha-2 country filter, e.g. US, GB, JP.
`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

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: counts are computed over a stored directory (not live), and they are scoped by the same filter set as the search tool, which affects how results should be interpreted. Return shape is left to the output schema.

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?

Three tight sentences with zero waste: purpose and allowed facet values first, filter-scoping behavior second, the practical discovery tip last. Everything is front-loaded and each sentence adds information.

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

Completeness4/5

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

Given 17 parameters, an existing output schema, and annotations covering read-only behavior, the description covers what an agent needs: what is aggregated, which facets exist, and how filters apply. A hint about cardinality or ordering of returned counts would round it out, but nothing essential is missing.

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 17 parameters are already documented, establishing a baseline of 3. The description earns an extra point by explaining that all filter parameters mirror the search tool and by specifying which facet values are valid for the required parameter, adding semantics the schema alone doesn't convey about filter reuse.

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 ('Returns facet counts over the stored Apple Maps place directory') and enumerates the exact facetable fields. This clearly separates it from siblings like datasets_apple_maps_places_search and _nearby, which return records rather than aggregates.

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?

Explicitly tells the agent that the tool takes the same filters as the search tool to scope counts, and gives a concrete workflow: use facet=category to discover valid category filter values. It does not state when to avoid using it (e.g. when record-level results are needed), so it falls just short of a 5.

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.