Skip to main content
Glama
Sign In
Apple Store MCP

Apple Store MCP

by washedguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_configuration_options

Retrieve live Apple product configuration options and price deltas for a collection and current selections, helping users compare upgrade choices and refine a build.

Instructions

Get live configuration choices and relative price deltas. Upgrade choices may require changing other dimensions; they are not necessarily compatible. The selected price and deltas come from Apple and depend on the returned selected dimensions. Identifiers and coverage vary by product and storefront.

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": {
      "collection": "<collection>",
      "selections": "<selections>"
    },
    "name": "get_configuration_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
collectionYesApple configurator collection identifier from a buy page, e.g. MBP_2026_COLLECTION.
selectionsYesApple dimension identifiers and selected values. Use returned dimension names and values to refine selections; availability depends on the product.

Output Schema

NameRequiredDescriptionDefault
resetYes
countryYes
currencyYes
languageYes
collectionYes
dimensionsYes
observed_atYes
part_numberYes
selected_priceYesApple's price for the returned selection, if supplied. Check the display text for qualifiers such as 'from'.
selected_dimensionsYes
requested_selectionsYes
container_part_numberYes
product_configurationYes
selected_price_displayYesApple's price text including any starting-price qualifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries real weight: it discloses that options are live, that price deltas originate from Apple but are contingent on the returned selected dimensions, that upgrade choices are not necessarily compatible, and that identifiers/coverage vary by product and storefront. It still omits error behavior for invalid or incompatible selections and any auth/rate-limit context, so it is strong but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the capability and followed by the caveats that matter for correct invocation. Each sentence contributes, though the final sentence about identifiers and coverage varying is somewhat terse and could be merged or sharpened.

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?

The tool has a nested-object parameter and an output schema, so return-value explanation is unnecessary, and the description covers the non-obvious behaviors (live data, Apple-sourced deltas, interdependence of dimensions). What is missing is guidance on failure modes for incompatible combinations and its place in the broader product/configuration toolset.

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 coverage is 100% and the parameter descriptions already explain country, language, collection, and the dimension/value map for selections. The description only reinforces that deltas depend on the returned selected dimensions, adding reinforcement rather than new meaning, so the baseline 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?

The description opens with a specific verb and resource: 'Get live configuration choices and relative price deltas', which tells an agent exactly what the tool returns. It never names a sibling or states how it differs from get_configuration_pickup, check_configuration_delivery, or get_product, so it falls short of 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 Guidelines3/5

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

Usage is only implied: the caveat that 'Upgrade choices may require changing other dimensions' suggests an iterative refine-and-re-query loop, but the description never states when to call this versus the pickup/delivery siblings, nor what prerequisite (a collection id from a buy page) must be obtained first. The agent must infer the workflow.

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