Skip to main content
Glama
Sign In
Apple Store MCP

Apple Store MCP

by washedguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_configuration_pickup

Check price, configuration options, and nearby Apple Store pickup availability for a selected product configuration without reserving or buying it.

Instructions

Check price, options and nearby store availability for a configuration. Read-only: does not reserve or purchase anything. The returned configuration identifies the checked product. Apple may block or change the endpoint.

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>",
      "location": "<location>",
      "collection": "<collection>",
      "selections": "<selections>"
    },
    "name": "get_configuration_pickup"
  }
}

Input Schema

NameRequiredDescriptionDefault
buy_urlYesApple buy-page URL in 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 near the desired Apple stores.
collectionYesConfigurator collection identifier from the buy page.
selectionsYesSelected configuration dimension identifiers and values.

Output Schema

NameRequiredDescriptionDefault
noteYes
storesYes
countryYes
languageYes
observed_atYes
configurationYesPrice, options and selected configuration used for the availability check.
location_scopeYes
selected_dimensionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it explicitly says read-only, states that nothing is reserved or purchased, notes the returned configuration identifies the checked product, and warns that Apple may block or change the endpoint. It does not cover authentication, permissions, or rate limits, but it discloses the key behavior and side-effect profile.

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?

The description is front-loaded, with purpose first and safety caveats immediately after. Every sentence adds value, and there is no filler or redundant wording.

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 six-parameter tool with a nested selections object and an output schema, the description covers purpose, read-only behavior, return identification, and endpoint volatility. It does not add auth or rate-limit details, but parameter detail is fully handled by the schema and the output schema covers return values.

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 the schema already documents each parameter thoroughly. The description adds little parameter-level meaning beyond noting that the returned configuration identifies the checked product, making the baseline 3 appropriate.

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: checking price, options, and nearby store availability for a configuration. It distinguishes itself from delivery-oriented siblings by emphasizing nearby store availability, though it does not name those siblings explicitly.

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?

The read-only and no-reservation statements clarify safe usage, but the description does not explicitly say when to choose this tool over check_configuration_delivery or check_variant_pickup. Usage is implied by the pickup-availability framing rather than stated as routing 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