wostrom.de Preisvergleich

Server Details

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

TDQS

A4.2/5.0

Scored 2026-09-23 20:05 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: search_offers finds products via search criteria while lookup_product retrieves a specific product by ID or URL. They reference each other's outputs (externalId from search_offers), making them complementary rather than overlapping.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern: 'lookup_product' and 'search_offers'. Both verbs clearly indicate the action and the noun indicates the target, even though 'lookup' and 'search' are different verbs, their use is predictable.

Tool Count3/5

With only two tools, the server feels slightly thin for a general price-comparison service. That said, the pair covers both discovery and specific product lookup, which is a minimal but coherent scope, so it lands on the borderline side of appropriateness.

Completeness4/5

The tool set provides the essential operations: searching the catalog and fetching a detailed product view. There are no obvious dead ends since lookup_product accepts the ID returned by search_offers. Minor gaps like category browsing or price-alert creation exist, but they are not critical for the stated purpose.

Available Tools

2 tools

lookup_productProdukt auf wostrom.de per ID/URL nachschlagenA

Read-onlyIdempotent

Inspect

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description reinforces these by stating 'read-only' and listing output data. It adds context about the returned fields (best price, price statistics, link) beyond annotations.

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 bilingual and contains two sentences covering both German and English. It is concise but could be slightly more streamlined by removing the repetition.

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 tool has an output schema (though not shown), the description adequately explains what the tool returns. It covers the parameters and usage constraint, making it complete for the agent.

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% with clear descriptions for id and url. The description adds the constraint 'Exactly one of id/url must be given', which goes beyond the schema's optional parameters.

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 delivers best price, price statistics, and offer link. It distinguishes from sibling search_offers by focusing on a single 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 Guidelines3/5

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

The description mentions exactly one of id/url must be given but does not explicitly guide when to use this tool versus the sibling search_offers. Implicit understanding is that this is for specific product lookup, not searching.

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

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

Read-onlyIdempotent

Inspect

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

Behavior5/5

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint false; the description adds meaningfully richer behavior: it is explicitly read-only, discloses that purchases happen at the linked merchant as affiliate with unchanged price, and explains the full-catalog scope and the 30-day price-trend signal (priceStats.isLowest30d). No contradiction with annotations exists.

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 description is front-loaded with the trigger condition and is information-dense, but the final English sentence repeats almost exactly what the German part already says. The output-field enumeration is also longer than necessary because an output schema exists, so some sentences do not earn their place.

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?

The description covers when to use it, geographic and currency scope, indexed sources, filter options, returned fields including facets and detailUrl, affiliate/read-only behavior, and the meaning of the 30-day-low flag. Combined with the full input and output schemas and annotations, nothing essential is missing for correct invocation.

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%, so the baseline is 3. The description only restates the filter dimensions (Suchbegriff, Marke, Preisspanne) and mentions facets, without adding format, constraints, or semantics beyond what the input schema already documents for query, brand, minPrice, maxPrice, and limit.

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 starts with a specific verb and resource: it finds the cheapest current price for 'strom' in Germany across Amazon, eBay and AliExpress, and describes it as a full-catalog search with filters. It is clear what the tool does, but it never explicitly contrasts itself with the sibling lookup_product, so the differentiation is left to the reader.

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 includes an explicit trigger list: use when the user asks for price, offer, 'guenstig', 'wo kaufen', or a specific 'strom'. However, it gives no when-not guidance and does not point to lookup_product as the alternative for exact or single-product lookup.

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

wospeicher.de Preisvergleich A
de.wospeicher
Deutscher Preisvergleich für Stromspeicher – Bestpreis-Suche (read-only).
Energy E-commerce & Retail
22
wosolar.de Preisvergleich A
de.wosolar
Deutscher Preisvergleich für Solaranlagen & Balkonkraftwerke – Bestpreis-Suche (read-only).
Energy E-commerce & Retail
22
wohandy.de Preisvergleich A
de.wohandy
Deutscher Preisvergleich für Handys – 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

Related MCP Servers

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
-
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
SwitchAI
Energy Autonomous Agents
US1929
A
license
A
quality
C
maintenance
AI agent for Italian energy tariff comparison. Analyzes electricity and gas bills, compares 44+ offers from 13 providers, estimates savings with full ARERA regulated cost breakdown
Updated a month ago (2026-08-21 05:39 UTC)
7
MIT
gridhub-mcp
Energy Open Data
jalcodev
A
license
A
quality
B
maintenance
Live and historical electricity prices, demand, generation mix and carbon intensity for 25 grid zones (US, Europe, GB, Australia). Hosted endpoint plus local stdio bridge; free sample mode, free API key, or x402 pay-per-call.
Updated a month ago (2026-08-29 15:40 UTC)
6
MIT

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?

Server Details

TDQS

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Elecz MCP Server

geizhals-mcp

SwitchAI

gridhub-mcp

Glama MCP Gateway

Resources