wohandy.de Preisvergleich

Server Details

Deutscher Preisvergleich für Handys – 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: 99.9% over 46 days
Last Tested: 2026-10-02 11:15
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.6/5.0

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

Disambiguation5/5

lookup_product is explicitly for known IDs or Amazon URLs, while search_offers handles keyword/brand/price queries, so there is no real ambiguity. Their inputs and outputs are complementary rather than overlapping.

Naming Consistency5/5

Both tool names follow the same verb_noun snake_case pattern (lookup_product, search_offers). The naming is predictable and matches the action each tool performs.

Tool Count4/5

Two tools is on the low end, but the server has a deliberately narrow read-only price-comparison scope. Search plus direct product lookup covers the core use case without feeling padded.

Completeness5/5

For a price-comparison server, the surface is complete: agents can search the full catalog, refine by filters, and look up specific products by ID or URL. Since the domain is read-only, the absence of create/update/delete operations is not a gap.

Available Tools

2 tools

lookup_productProdukt auf wohandy.de per ID/URL nachschlagenA

Read-onlyIdempotent

Inspect

Schlaegt ein konkretes Produkt im aktuellen wohandy.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 wohandy.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

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description confirms 'read-only' and adds detail about returned data (best price, statistics, link), providing complete behavioral context.

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 concise, two sentences, front-loading key information in German and English. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and annotations, the description fully covers purpose, parameter constraints, and return value highlights. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions (100% coverage). Description adds critical constraint that exactly one must be provided and clarifies that URL is an Amazon product link with ASIN extraction.

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 clearly states the tool looks up a specific product by ID or URL and returns best price, 30-day statistics, and offer link. It distinguishes from the sibling tool 'search_offers' which is for searching multiple products.

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 requires exactly one of id or url to be provided. It implies usage when a specific product identifier is known, but could be more explicit about when not to use it vs. search_offers.

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

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

Read-onlyIdempotent

Inspect

Findet Handys zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wohandy.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Handy 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 Handys 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.3/5.0

Behavior5/5

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

Annotations already mark it read-only/idempotent/non-destructive, and the description adds substantial context: full-catalog search over hundreds of products, 30-day price-trend field semantics (priceStats.isLowest30d), facet refinement, direct purchase links, and affiliate disclosure with unchanged price. No contradiction with annotations.

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

Conciseness3/5

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

The German portion is well front-loaded and information-dense, but the English sentence at the end largely repeats the German opening and result summary. This duplication prevents the description from being maximally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given optional parameters, existing output schema, and read-only annotations, the description covers when to use, what is searched, what is returned, how to refine via facets, and the affiliate behavior. Nothing material is missing for an agent to select and invoke the tool correctly.

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%, and the schema already defines query, brand, minPrice, maxPrice, and limit precisely. The description adds only a general 'filterbar per Suchbegriff, Marke und Preisspanne' mapping, which is useful but does not go beyond the schema baseline.

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 opens with a specific verb+resource ('Findet Handys zum guenstigsten aktuellen Preis in Deutschland') and defines geographic scope, marketplace coverage, and result semantics. It positions this as a catalog-wide price search tool with filters, which implicitly differentiates it from the sibling lookup_product for exact product lookups.

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?

It gives explicit invocation triggers ('Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, guenstig, wo kaufen oder einem konkreten Handy fragt'). It does not name when-not-to-use conditions or explicitly route to lookup_product, so it falls just short of the fullest guidance.

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

wotablet.de Preisvergleich A
de.wotablet
Deutscher Preisvergleich für Tablets – 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
wokonsole.de Preisvergleich A
de.wokonsole
Deutscher Preisvergleich für Spielekonsolen – 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 a day ago (2026-10-01 10:29 UTC)
4
MIT
geizhals-mcp
E-commerce & Retail Web Scraping
spinnerich
A
license
A
quality
D
maintenance
Enables searching geizhals.de for products and retrieving shop prices and offers to assist with price comparison.
Updated 3 months ago (2026-06-21 15:30 UTC)
2
MIT
TrustRails MCP Server
E-commerce & Retail Search
james-webdev
A
license
A
quality
C
maintenance
Searches UK electronics products across multiple retailers, compares prices, and provides purchase links.
Updated 2 days ago (2026-09-30 18:24 UTC)
2
133 npm
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