Skip to main content
Glama
Sign In
Apple Store MCP

Apple Store MCP

by washedguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_delivery

Read current delivery estimates for selected product variants and a postal code without making a purchase or reservation; missing estimates mean unknown, not unavailable.

Instructions

Read current delivery estimates for product variants and a postal code. No purchase or reservation is made. A missing estimate means unknown, not unavailable.

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>",
      "postal_code": "<postal_code>"
    },
    "name": "check_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
buy_urlYesApple buy-page URL for the selected storefront.
countryNoStorefront country code, e.g. us, de, fr, ch, be. Use list_storefronts for supported values.us
languageNoShop language; defaults to the country's main language. Switzerland: de/fr; Belgium: fr/nl; Canada: en/fr.
postal_codeYesDelivery postal code.
part_numbersYesProduct part numbers returned by get_product.

Output Schema

NameRequiredDescriptionDefault
countryYes
languageYes
productsYes
observed_atYes
postal_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/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, and it does disclose two genuinely useful behavioral traits: the call is non-committal ('No purchase or reservation is made') and a missing estimate must be read as unknown rather than unavailable. That is real value beyond what an agent could infer from the schema. It omits any mention of authentication, rate limits, or whether estimates are cached/live.

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 short sentences, front-loaded with the core action and immediately followed by the two constraints an agent most needs (read-only, missing-means-unknown). No filler or restated title.

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, so return-value explanation is unnecessary, and the full parameter set is described in the schema. The description adds the semantics needed to interpret an empty result. The remaining gap is disambiguation from the pickup and configuration-delivery siblings, which for a 12-tool catalog matters.

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 every parameter is already documented in structured form (buy_url, country, language, postal_code, part_numbers). The description adds no meaning beyond 'product variants and a postal code,' simply restating two of the five inputs. Baseline 3 is appropriate when the schema does the work.

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: 'Read current delivery estimates for product variants and a postal code.' That is concrete and lets an agent distinguish it from pickup-oriented siblings by the resource (delivery estimates) and inputs (part numbers + postal code). It stops short of naming or contrasting any sibling explicitly, which keeps it from a 5.

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 mention of the closely related siblings (check_variant_pickup, check_configuration_delivery) that an agent would need to choose between delivery estimates for a standalone part versus a configured build or a store-pickup estimate. 'A missing estimate means unknown, not unavailable' is result-interpretation guidance, not selection guidance.

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

Deploy Server

Other Tools