wospeicher.de Preisvergleich

Server Details

Deutscher Preisvergleich für Stromspeicher – 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 22:22
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.3/5.0

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

Disambiguation5/5

The two tools have clearly distinct purposes: search_offers discovers products with filtering, while lookup_product retrieves details for a specific known product by ID or URL. There is no functional overlap, and descriptions reinforce the boundary.

Naming Consistency5/5

Both tool names follow the same lowercase verb_noun convention: 'lookup_product' and 'search_offers'. Though the verbs differ, the pattern is identical and predictable.

Tool Count3/5

Two tools is thin for a price-comparison server, but it may be sufficient for a read-only catalog with search and detail lookup. The count feels borderline rather than clearly complete.

Completeness4/5

The core user journey (search for offers, then look up a specific product) is covered, and search facets provide browsing. Minor gaps exist, such as no dedicated category or popular-products endpoint, but the surface is workable for its stated purpose.

Available Tools

2 tools

lookup_productProdukt auf wospeicher.de per ID/URL nachschlagenA

Read-onlyIdempotent

Inspect

Schlaegt ein konkretes Produkt im aktuellen wospeicher.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 wospeicher.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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds concrete return values (best price, 30-day stats, offer link) and confirms the read-only nature. No contradictions.

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 with two bilingual sentences plus a clear constraint. No redundancy or wasted words.

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 output schema exists, the description sufficiently covers inputs, returns, and constraints. No significant missing context for a read-only lookup tool.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds meaning by explaining the 'id' as ASIN/externalId and 'url' as an Amazon product URL, plus the constraint to provide exactly one.

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 it looks up a specific product by ID or URL and returns best price, statistics, and link. It distinguishes from the sibling 'search_offers' by the precise lookup mechanism, though not explicitly contrasting.

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 mandates exactly one of 'id' or 'url' must be provided ('Genau eines der Felder'), and specifies what the tool returns. It does not explicitly contrast with 'search_offers' but the context implies use when a specific identifier is known.

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

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

Read-onlyIdempotent

Inspect

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

Behavior5/5

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

The description adds substantial behavioral context beyond annotations: it covers the full catalog (several hundred products), explains the 30-day trend semantics (priceStats.isLowest30d), discloses affiliate/referral nature with unchanged price, mentions read-only status, and clarifies that results include facets, a direct buy-link, and a citable product page. This is far beyond the minimal annotation hints.

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 information-dense but somewhat long and repetitive (German and English versions say the same thing). The front-loaded German sentence is clear, the English duplicate could be trimmed. Every sentence adds value, but the bilingual repetition costs a point.

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?

For a read-only search tool with 5 optional params, a full schema, an output schema, and explicit return fields, the description is complete. An agent knows exactly what triggers the tool, what it returns, how filtering works, and that it's safe. Nothing critical is missing.

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

Parameters4/5

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

Schema coverage is 100% and each parameter already has a description with examples. The tool description adds a bit more by clarifying how brand and query interact with facets ('exakter Wert aus facets.marke') and that limit defaults to 24. Since the schema already carries full weight, the description's contribution is modest but non-redundant.

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 ('Findet', 'search') and resource ('Stromspeicher' with best-price comparison across Amazon, eBay, AliExpress). It clearly distinguishes the tool by its purpose: finding cheapest current prices and comparing offers across three marketplaces. It also differentiates from the sibling 'lookup_product' by emphasizing price comparison rather than a simple product lookup.

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

Usage Guidelines5/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 for price, offer, 'guenstig', 'wo kaufen', or a specific Stromspeicher. It also names the sibling 'lookup_product' indirectly by framing this as the price-comparison tool. While it doesn't explicitly say 'use lookup_product for X instead', the clear trigger conditions and the catalog-wide search are strong usage 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

wosolar.de Preisvergleich A
de.wosolar
Deutscher Preisvergleich für Solaranlagen & Balkonkraftwerke – Bestpreis-Suche (read-only).
Energy E-commerce & Retail
22
wostrom.de Preisvergleich A
de.wostrom
Deutscher Preisvergleich für Strom-Produkte – Bestpreis-Suche (read-only).
E-commerce & Retail Energy
22
woebike.de Preisvergleich A
de.woebike
Deutscher Preisvergleich für E-Bikes – Bestpreis-Suche (read-only).
E-commerce & Retail Search
22
woroller.de Preisvergleich A
de.woroller
Deutscher Preisvergleich für E-Roller – 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
Elecz MCP Server
Energy Open Data
zemloai-ctrl
F
license
Not graded
quality
C
maintenance
Provides real-time electricity prices, cheapest hours, and contract comparison for 40+ countries, enabling AI agents to make energy-aware decisions.
Updated 3 months ago (2026-07-07 16:39 UTC)
4
-
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
EcoBack Raumklima MCP
Energy Weather Services
f-tiger
F
license
Not graded
quality
D
maintenance
Nine tools for indoor climate and household energy in Germany/EU: BTU sizing for a room, portable-AC window-seal length, live heatwave outlook, appliance running costs, heating watts, dew point for safe ventilation, and balcony-storage subsidy rules. Also searches and reads 133 guides on getecoback.com; no auth, no personal data, and every answer returns its source URL.
Updated a month ago (2026-08-29 11:41 UTC)
-