wostrom.de Preisvergleich

strom in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)

search_offers

Read-onlyIdempotent

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 ~150 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.

Input Schema

TableJSON 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

TableJSON 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.4/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 adds behavioral context: it confirms read-only nature, explains affiliate links with unchanged prices, describes the output (title, best price, brand, image, 30-day trend, attributes, direct link, detail URL, facets). 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.

Conciseness4/5

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

The description is well-structured: purpose first, then usage guidance, then what it searches, output details, and a read-only note. It is slightly repetitive with both German and English, but not overly verbose. Every sentence adds value.

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?

With an output schema indicated, the description explains all output fields and includes facets for further filtering. All 5 optional parameters are explained. The sibling tool context is clear. The description is complete for an agent to use correctly.

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?

Input schema covers all 5 parameters with descriptions (100% coverage). The description adds extra context: filterable by brand, price range, and mentions facets in output for refinement. This reinforces parameter usage beyond the schema.

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 it finds the cheapest current price for 'strom' across Amazon, eBay, and AliExpress, with a price comparison from wostrom.de. It explicitly says when to use (for price, offer, cheap, where to buy queries) and distinguishes from sibling 'lookup_product' by being a search across multiple sellers for best price.

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 to use this tool when a user asks for price, offer, cheap, where to buy, or a specific product query. It does not explicitly exclude when not to use or mention alternative 'lookup_product' for single product details, but the context is strong enough for an agent to infer.

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

All wostrom.de Preisvergleich tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a distinct purpose: search_offers finds products by query, lookup_product retrieves details by ID/URL. No overlap.

Naming Consistency5/5

Both tools follow a clear verb_noun pattern (search_offers, lookup_product) with consistent snake_case.

Tool Count3/5

Two tools is on the lower end of appropriate for a price comparison server, but covers search and lookup. Could benefit from additional tools like category browsing.

Completeness3/5

The set covers core operations (search and lookup) but lacks features like filtering, comparison, or historical trends beyond 30 days.

Resources

Need Help?