Skip to main content
Glama

datasets_apple_maps_places_search

Read-only

Search the stored Apple Maps place directory by keyword, category, city, state, country, rating or radius and return places with name, category, address, coordinates, phone, website, hours and rating. Coverage is observed, not complete (Apple answers each crawl search with at most 25 places). Costs 1 credit per record returned (minimum 2), so keep page_size to what you need. Use datasets_apple_maps_places_facets to discover exact category names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datasets_apple_maps_places_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional full-text search over place name, category, city and address; every term must match. Max 256 characters.
latNoOptional latitude for radius filtering or distance sort, from -90 through 90; supply together with lon.
lonNoOptional longitude for radius filtering or distance sort, from -180 through 180; supply together with lat.
cityNoOptional exact city filter, max 128 characters.
pageNoResult page number, 1-based, default 1; page times page_size must not exceed 10000.
sortNoOptional sort order. Allowed values: relevance, rating_desc, review_count_desc, updated_at_desc, distance_asc. Defaults to relevance with q, otherwise updated_at_desc.
stateNoOptional exact state/region filter, max 128 characters.
categoryNoOptional exact Apple category name, max 128 characters, e.g. Coffee Shop; use facet=category to discover values.
radius_mNoOptional radius in meters, from 1 through 50000; requires lat and lon.
has_phoneNoOptional phone presence filter; true keeps only places with a phone number.
page_sizeNoPage size, default 20, max 100; page times page_size must not exceed 10000.
min_ratingNoOptional minimum rating, from 0 through 5. Places Apple shows no rating for have rating null; any value above 0 excludes them.
has_websiteNoOptional website presence filter; true keeps only places with a website.
postal_codeNoOptional exact postal code filter, max 128 characters.
country_codeNoOptional ISO 3166-1 alpha-2 country filter, e.g. US, GB, JP.
min_rating_countNoOptional minimum number of ratings behind the rating, 0 or greater.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds important behavior beyond the annotations: coverage is observed rather than complete, Apple returns at most 25 places per crawl search, and each returned record costs 1 credit with a minimum of 2. These are high-value operational facts that an agent would not get from readOnlyHint/openWorldHint alone.

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?

The description is front-loaded with the core purpose, then adds coverage, cost, and sibling-routing guidance in a compact form. Every sentence provides useful information, with no filler or redundant restatement of the tool name.

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 16 optional parameters, full schema descriptions, an output schema, and read-only annotations, the description covers the critical behavioral caveats: incomplete coverage, per-record cost, page_size caution, and category facet discovery. Nothing essential for correct invocation 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 schema already fully documents all 16 parameters and the baseline would be 3. The description adds useful meaning beyond the schema by tying page_size to credit cost and by pointing category filtering to the facets tool for exact values.

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 states a specific verb and resource: search the stored Apple Maps place directory. It enumerates the supported filter dimensions and returned fields, and it explicitly routes category discovery to datasets_apple_maps_places_facets. This is enough for an agent to distinguish it from the facets sibling, though it could also explicitly contrast with datasets_apple_maps_places_nearby.

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 gives clear usage guidance for category filtering by naming datasets_apple_maps_places_facets as the alternative for discovering exact category names. It also warns about credit cost and advises keeping page_size to what is needed. It does not explicitly state when to prefer this over nearby/item/place sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.