wosneaker.de Preisvergleich

Server Details

Deutscher Preisvergleich für Sneaker – Bestpreis-Suche (read-only).

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 42 days
Last Tested: 2026-09-28 21:57
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.1/5.0

Scored 2026-09-23 23:10 across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: search_offers handles broad discovery by keyword/brand/price, while lookup_product resolves a specific product by ID or URL. There is no meaningful overlap that would confuse an agent.

Naming Consistency5/5

Both tool names follow a consistent verb_noun snake_case pattern: lookup_product and search_offers. The naming is predictable and aligns with each tool's action.

Tool Count4/5

Two tools is on the low end for a general-purpose server, but for a focused read-only price comparison domain, search plus direct product lookup covers the core workflow. Each tool earns its place, though a brand/category listing tool could have been added.

Completeness5/5

For a read-only price comparison use case, the surface is complete: users can discover products via search_offers with facets and filters, then retrieve detailed product price statistics and links via lookup_product. No obvious dead ends or missing critical operations exist.

Available Tools

2 tools

lookup_productProdukt auf wosneaker.de per ID/URL nachschlagenA

Read-onlyIdempotent

Inspect

Schlaegt ein konkretes Produkt im aktuellen wosneaker.de-Katalog per Produkt-ID (Amazon-ASIN bzw. externalId aus search_offers) ODER per Amazon-Produkt-URL nach. Liefert Bestpreis, 30-Tage-Preisstatistik und den Angebots-Link. Genau eines der Felder id/url angeben. Looks up a specific product in the wosneaker.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).

ParametersJSON Schema

Name	Required	Description	Default
`id`	No	Produkt-ID: Amazon-ASIN oder externalId.
`url`	No	Amazon-Produkt-URL (z.B. https://www.amazon.de/dp/B0ABC123DE) — die ASIN wird extrahiert.

Output Schema

ParametersJSON Schema

Name	Required	Description
`site`	No
`count`	Yes
`query`	No
`facets`	No	Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.
`products`	Yes
`updatedAt`	No
`disclosure`	No
`catalogVersion`	No

TDQS

A3.7/5.0

Behavior4/5

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

The description reveals what the tool returns (best price, 30-day stats, offer link) and confirms read-only behavior, aligning with annotations. It adds context beyond annotations by detailing the output scope.

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?

The description is concise and to the point, with both German and English versions provided. Key information is front-loaded, and there is no redundant text.

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?

Given the existence of an output schema, the description sufficiently covers inputs and the nature of the output. It mentions the key result components, making it complete for a lookup tool.

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?

The schema covers both parameters with descriptions. The description reiterates the constraint of using exactly one and clarifies that the URL is used for ASIN extraction, adding minimal extra meaning.

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 clearly states the tool looks up a specific product by ID or URL. It mentions the input sources (ASIN/externalId from search_offers) and distinguishes from sibling search_offers by targeting a single product.

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 description specifies that exactly one of 'id' or 'url' must be provided, which is a key usage constraint. However, it does not explicitly state when to use this tool versus the sibling 'search_offers' tool, though the intent is implied.

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

search_offersSneaker in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)A

Read-onlyIdempotent

Inspect

Findet Sneaker zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wosneaker.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Sneaker fragt. Durchsucht den vollen Katalog (mehrere hundert Produkte), filterbar per Suchbegriff, Marke und Preisspanne. Liefert je Produkt: Titel, Bestpreis, Marke, Bild, 30-Tage-Preistrend (priceStats.isLowest30d = aktuell guenstigster Stand), domain-spezifische Attribute (attributes, z.B. Leistung/Speicher/Farbe), einen direkten Kauf-Link (url) und eine zitierfaehige Produktseite (detailUrl). Die Antwort enthaelt zusaetzlich facets (verfuegbare Filterwerte) zum Verfeinern. Read-only, Kauf beim verlinkten Haendler (Affiliate, Preis unveraendert). Finds the cheapest current price in Germany for Sneaker across Amazon, eBay and AliExpress; returns best price, price trend, filter attributes and a direct link.

ParametersJSON Schema

Name	Required	Description
`brand`	No	Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. "Nike").
`limit`	No	Maximale Anzahl Ergebnisse (Default 24, max 100).
`query`	No	Suchbegriff, z.B. Modell/Marke/Eigenschaft ("Balkonkraftwerk 800W", "iPhone 15 schwarz"). Optional.
`maxPrice`	No	Hoechstpreis in EUR (optional).
`minPrice`	No	Mindestpreis in EUR (optional).

Output Schema

ParametersJSON Schema

Name	Required	Description
`site`	No
`count`	Yes
`query`	No
`facets`	No	Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.
`products`	Yes
`updatedAt`	No
`disclosure`	No
`catalogVersion`	No

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond that: it is an affiliate link scenario, the price for the buyer stays unchanged, and the search covers the full catalog of several hundred products. This is useful behavioral context, though it does not cover potential rate limits or other operational constraints.

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?

The description is front-loaded with purpose and usage, then gives detailed output semantics. However, the final English sentence largely repeats the opening German sentence, adding redundancy and making the description longer than necessary.

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 description covers when to use the tool, filtering capabilities, return fields, facets, and read-only affiliate behavior. Together with the output schema and annotations, this is nearly complete, but it could be improved by explicitly noting when not to use it relative to lookup_product.

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 input schema already documents all five parameters. The description reinforces that results are filterable by search term, brand, and price range, but it does not add substantial meaning beyond what the schema already provides.

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?

The description states a specific verb and resource: it finds the cheapest current Sneaker price in Germany across Amazon, eBay, and AliExpress. It also distinguishes itself by describing full-catalog search and price comparison, which separates it from the more targeted sibling tool lookup_product.

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?

The description explicitly says when to use the tool: when a user asks about price, offers, 'cheap', 'where to buy', or a specific Sneaker. It gives clear context for when this tool is appropriate, but it does not mention exclusions or contrast the sibling tool lookup_product.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesJul 7, 2026

Changedlookup_product5 fields changed

addedOutput schema / properties / facets

Added value: +{
+  "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.",
+  "type": "array"
+}

addedOutput schema / properties / products / items / properties / attributes

Added value: +{
+  "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.",
+  "type": "object"
+}

addedOutput schema / properties / products / items / properties / brand
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / products / items / properties / detailUrl

Added value: +{
+  "description": "Zitierfaehige Produktseite mit Preisverlauf.",
+  "type": "string"
+}

addedOutput schema / properties / products / items / properties / priceStats / description
```
Added value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
```

Changedsearch_offers11 fields changed

addedInput schema / properties / brand

Added value: +{
+  "description": "Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. \"Nike\").",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Maximale Anzahl Ergebnisse (Default 24, max 50)."New value: +"Maximale Anzahl Ergebnisse (Default 24, max 100)."

changedInput schema / properties / limit / maximum
```
Previous value: -50New value: +100
```

addedInput schema / properties / maxPrice

Added value: +{
+  "description": "Hoechstpreis in EUR (optional).",
+  "type": "number"
+}

addedInput schema / properties / minPrice

Added value: +{
+  "description": "Mindestpreis in EUR (optional).",
+  "type": "number"
+}

changedInput schema / properties / query / description

Previous value: -"Optionaler Suchbegriff — filtert nach Titel, Marke oder Haendler."New value: +"Suchbegriff, z.B. Modell/Marke/Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15 schwarz\"). Optional."

addedOutput schema / properties / facets

Added value: +{
+  "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.",
+  "type": "array"
+}

addedOutput schema / properties / products / items / properties / attributes

Added value: +{
+  "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.",
+  "type": "object"
+}

addedOutput schema / properties / products / items / properties / brand
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / products / items / properties / detailUrl

Added value: +{
+  "description": "Zitierfaehige Produktseite mit Preisverlauf.",
+  "type": "string"
+}

addedOutput schema / properties / products / items / properties / priceStats / description
```
Added value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
```

2 tool updatesJul 6, 2026
- First observedlookup_product
- First observedsearch_offers

Related MCP Connectors

wouhr.de Preisvergleich A
de.wouhr
Deutscher Preisvergleich für Uhren – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22
wolaptop.de Preisvergleich A
de.wolaptop
Deutscher Preisvergleich für Laptops – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22
wohandy.de Preisvergleich A
de.wohandy
Deutscher Preisvergleich für Handys – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22
woebike.de Preisvergleich A
de.woebike
Deutscher Preisvergleich für E-Bikes – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22

Related MCP Servers

geizhals-mcp
E-commerce & Retail Search
Samxel
A
license
Not graded
quality
B
maintenance
Enables AI to search Geizhals price-comparison data, including products, best prices, price history, ratings, categories, and deals.
Updated 3 days ago (2026-09-26 08:50 UTC)
4
MIT
idealo MCP Serverofficial
E-commerce & Retail Search
idealo
A
license
Not graded
quality
F
maintenance
Enables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).
Updated 4 months ago (2026-05-20 10:01 UTC)
19
MIT
ShopSignal
E-commerce & Retail Search
codesk90
F
license
Not graded
quality
D
maintenance
DTC competitor intelligence: catalog snapshots, price history, cross-brand product comparison, and drop/restock detection for 84 Shopify-powered brands. Pay-per-call via Apify.
Updated 4 months ago (2026-05-22 22:28 UTC)
-
Sneaker Catalog MCP Server
RAG Systems E-commerce & Retail
KeeperSolutions
F
license
Not graded
quality
B
maintenance
Provides tools for searching a sneaker catalog (hybrid keyword and semantic search), retrieving product details, and checking inventory stock.
Updated 2 months ago (2026-08-07 10:33 UTC)
-