Apple Store MCP

Overview Schema Source Related Servers Discussions Admin

find_stores

Locate Apple retail stores by city, region, or store name in a chosen country and get addresses, phone numbers, and coordinates.

Instructions

Find Apple retail stores in the selected country. Returns store names, addresses, phone numbers and coordinates where available.

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": {
      "query": "<query>"
    },
    "name": "find_stores"
  }
}

Input Schema

Name	Required	Description	Default
`fresh`	No	Bypass the process cache and request current shop data.
`query`	Yes	City, region, or store name in the selected country.
`country`	No	Storefront country code, e.g. us, de, fr, ch, be. Use list_storefronts for supported values.	us
`language`	No	Shop language; defaults to the country's main language. Switzerland: de/fr; Belgium: fr/nl; Canada: en/fr.

Output Schema

Name	Required	Default
`cache`	No
`count`	Yes
`query`	Yes
`stores`	Yes
`country`	No	us
`language`	No	en
`retailer`	Yes
`observed_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the returned fields, but omits anything about caching, freshness semantics (the schema's "fresh" flag implies a process cache the description never mentions), rate limits, or failure behavior for unmatched queries.

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 compact sentences, front-loaded with the purpose and followed by the return payload. No filler, no repetition of the title or name.

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?

Because an output schema exists, the description need not explain return values, and the schema fully documents the parameters. What remains missing is routing guidance against the store-listing sibling and any hint about cache/freshness behavior, which matters for a lookup whose results can go stale.

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 all four parameters (query, country, language, fresh) are already documented in the schema, including country codes and language fallbacks. The description adds only the phrase "in the selected country" and no new semantics, so the baseline 3 applies.

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?

"Find Apple retail stores in the selected country" gives a specific verb and resource, and the second sentence narrows the output to names, addresses, phones and coordinates. It does not distinguish itself from the sibling list_apple_stores, so an agent must infer which lookup to pick.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. With a sibling called list_apple_stores present in the catalog, the agent gets no statement of when a keyword query is the right choice versus a plain listing.

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

Deploy Server