Apple Store MCP

Overview Schema Source Related Servers Discussions Admin

compare_availability

Compare Apple Store pickup and delivery estimates across product variants and locations, with unknown status for failed or missing checks. Read-only; no reservations or purchases.

Instructions

Compare pickup and delivery estimates for variants. Failed, missing and unchecked results are reported as unknown. Read-only; does not reserve or purchase.

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": {
      "buy_url": "<buy_url>",
      "part_numbers": "<part_numbers>"
    },
    "name": "compare_availability"
  }
}

Input Schema

Name	Required	Description	Default
`buy_url`	Yes	Apple buy-page URL for the selected storefront.
`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.
`all_stores`	No	Check the country directory and attempt every listed store; limited to countries with at most 30 stores.
`part_numbers`	Yes	Part numbers to compare.
`pickup_locations`	No	Cities or postal codes to search for nearby stores.
`delivery_postcodes`	No	Postcodes to check for delivery estimates.

Output Schema

Name	Required	Description	Default
`note`	Yes
`errors`	Yes
`pickup`	Yes
`country`	Yes
`complete`	Yes
`delivery`	Yes
`language`	Yes
`observed_at`	Yes
`part_numbers`	Yes
`missing_parts`	Yes
`unknown_parts`	Yes
`missing_stores`	Yes
`unknown_delivery`	Yes
`directory_checked`	Yes
`directory_store_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations supplied, the description does useful work by declaring read-only semantics and that no reservation or purchase occurs, and by explaining how failures surface ('unknown'). It omits other behaviorally relevant traits an agent would want, such as that all_stores is capped at countries with 30 or fewer stores and that broad scans are likely slow or partial.

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, front-loaded with the purpose, followed by the result-semantics and safety caveat. Nothing is wasted and no sentence restates the name.

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?

An output schema exists and the input schema is fully documented, so the description only needs to cover scope and semantics, which it largely does. The remaining gap is the absence of routing guidance toward the single-variant siblings for a seven-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 description coverage is 100%, so the schema already documents buy_url, country, language, all_stores, part_numbers, pickup_locations, and delivery_postcodes. The description adds a small amount of framing by tying the comparison to variants and clarifying that unchecked inputs come back as unknown, which is beyond schema syntax.

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 states a specific verb and resource ('Compare pickup and delivery estimates for variants'), which is clearly distinct from a single-item check. It stops short of naming which sibling performs the single-variant version, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the word 'compare' and the multi-part-number schema, and the read-only/non-purchasing note scopes it as an informational tool. There is no explicit statement of when to pick this over check_delivery or check_variant_pickup, nor any preconditions such as needing a valid buy_url from a storefront.

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

Deploy Server