Skip to main content
Glama
Sign In
Apple Store MCP

Apple Store MCP

by washedguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_configuration_delivery

Checks delivery estimates for a configured Apple product using buy URL, collection, selections, and postal code. Returns checked configuration without purchase or reservation.

Instructions

Check delivery estimates for a configurable product. The returned configuration identifies the checked selections. No purchase or reservation is made; a missing estimate is unknown.

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>",
      "collection": "<collection>",
      "selections": "<selections>",
      "postal_code": "<postal_code>"
    },
    "name": "check_configuration_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.
collectionYesConfigurator collection identifier.
selectionsYesSelected configuration dimensions and values.
postal_codeYesDelivery postal code.

Output Schema

NameRequiredDescriptionDefault
countryYes
languageYes
productsYes
observed_atYes
postal_codeYes
configurationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does deliver the two most important behavioral facts: it is non-mutating ("No purchase or reservation is made") and a missing estimate means unknown rather than an error. It still omits auth requirements, failure modes for bad postal codes, and any latency/rate-limit context.

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 with the core action first, then the return semantics, then the non-mutation guarantee. Every sentence carries distinct information and none is filler.

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?

An output schema exists so return values need no prose, all parameters are fully described in the schema, and the description covers the two things structured fields cannot express: no side effects and how to read a missing estimate. Nothing essential to correct invocation is absent.

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 six parameters including the nested selections object are already documented in the schema. The description adds no parameter-level meaning, so the baseline of 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?

States a specific verb and resource: "Check delivery estimates for a configurable product." The qualifier "configurable product" implicitly separates it from the plain delivery-check sibling, but no sibling is named, so an agent must infer the distinction.

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 only implied by the phrase "configurable product"; there is no explicit statement of when to prefer this over check_delivery or check_variant_pickup, and no prerequisites such as needing a resolved buy_url/collection first. The agent can guess the context but receives no routing rule.

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