MediaMarkt & Saturn MCP

Overview Schema Source Related Servers Discussions Admin

check_pickup_availability

Check whether selected products are available for pickup at a specific MediaMarkt or Saturn store using product and store IDs from search results and store lookup.

Instructions

Check pickup availability for products at one selected store. Use IDs from search_products and find_stores for the same retailer and country. Unknown means the retailer returned no status; a status for an unverified ID does not confirm the product exists. Availability is not a reservation or exact stock count.

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": {
      "store_id": "<store_id>",
      "product_ids": "<product_ids>"
    },
    "name": "check_pickup_availability"
  }
}

Input Schema

Name	Required	Description	Default
`fresh`	No	Bypass the process cache and request current shop data.
`country`	No	Storefront country code. Defaults to de. Product and store IDs are country-specific.	de
`language`	No	Shop language; defaults to the country's main language. Switzerland: de/fr/it; Belgium: nl/fr.
`retailer`	No	Storefront brand: mediamarkt (including MediaWorld in Italy) or saturn (Germany only).	mediamarkt
`store_id`	Yes	Store ID returned by find_stores for the same retailer.
`product_ids`	Yes	One to 48 product IDs returned by search_products.

Output Schema

Name	Required	Default
`cache`	No
`count`	Yes
`country`	No	de
`language`	No	de
`products`	Yes
`retailer`	Yes
`store_id`	Yes
`checked_at`	Yes
`observed_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Nov 11, 2026

TDQS

A4.2/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 disclosure burden and does meaningful work: it explains the 'Unknown' status semantics, warns that a status for an unverified ID does not confirm the product exists, and clarifies that availability is neither a reservation nor an exact stock figure. It omits any mention of latency, caching, or rate limits, which the schema only hints at via the 'fresh' flag.

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?

Four short sentences, each doing distinct work: purpose, ID sourcing, status interpretation, and result caveats. The core action is front-loaded and there is no redundant restatement of the title or schema.

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 values need not be described, and the description correctly spends its words on interpretation semantics (Unknown, unverified IDs) that the output schema cannot convey. Coverage is strong for a six-parameter tool; only caching/freshness behavior and any failure modes are left implicit.

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 all six parameters including country-specific IDs and the 48-item cap. The description reinforces the cross-tool provenance of store_id and product_ids but adds little syntax or format meaning beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (check pickup availability) plus the scope constraint 'at one selected store', which is the key distinction from a general product lookup. It also names the sibling tools that supply the IDs (search_products, find_stores), so an agent can place it in a workflow without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a clear usage precondition: IDs must come from search_products and find_stores for the same retailer and country. It does not name an alternative tool or an explicit when-not-to-use case, but the sibling set contains no other availability tool, so the omission is minor.

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

Deploy Server