Skip to main content
Glama
Sign In
Apple Store MCP

Apple Store MCP

by washedguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_variant_pickup

Reads nearby Apple Store pickup availability estimates for product variants using part numbers and a city or postal code. Returns estimates only, not reservations or stock counts.

Instructions

Read pickup availability quotes for product variants at nearby stores. Results are estimates, not reservations or stock counts.

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>",
      "location": "<location>"
    },
    "name": "check_variant_pickup"
  }
}

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.
locationYesCity or postal code to find nearby stores.
part_numbersYesVariant part numbers returned by explore_product or get_product.

Output Schema

NameRequiredDescriptionDefault
storesYes
countryYes
languageYes
locationYes
observed_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 one genuinely useful behavioral trait: results are estimates rather than reservations or stock counts, which prevents the agent from treating output as authoritative inventory. It says nothing about authentication, rate limits, or latency, and "Read" only weakly implies read-only.

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, no filler, with the core purpose front-loaded and the caveat following. Every clause earns its place.

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?

For a read tool with five flat parameters and an output schema covering return values, the description covers purpose and the semantics of the result. The remaining gap is routing guidance among the many pickup/delivery/availability siblings, which the description never addresses.

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 five parameters are already documented in the schema, including country codes and part-number provenance. The description adds no parameter-level meaning beyond that, 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?

"Read pickup availability quotes for product variants at nearby stores" gives a specific verb (read pickup quotes), a specific resource (product variants), and scope (nearby stores). It contrasts implicitly with configuration-level siblings like check_configuration_pickup through the word "variants," though it never names an alternative explicitly.

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?

The description states what the tool returns but gives no when-to-use versus when-not guidance, even though siblings such as check_configuration_pickup, check_delivery, and compare_availability occupy adjacent territory. An agent must infer the correct choice from names alone.

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