wospeicher.de Preisvergleich

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

search_offers

Read-onlyIdempotent

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 ~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 Stromspeicher 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/5.0

Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, destructiveHint. The description adds behavioral details: read-only, affiliate links with unchanged prices, returns facets and a 30-day price trend (priceStats.isLowest30d). 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.

Conciseness3/5

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

The description is lengthy and mixes German and English, but it front-loads the main purpose. Some details could be condensed (e.g., repeated info about domains). It's functional but not optimally concise.

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 tool's complexity (multiple domains, price trends, facets, direct links), the description covers key output features. Output schema exists, so return value explanation is not required. Complete for an agent to understand its capabilities.

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?

Input schema has 100% coverage with descriptions for all 5 parameters. The description adds limited extra context (e.g., examples for query, reference to facets.marke for brand). Baseline is 3; minimal enhancement.

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's purpose: finding the cheapest current prices for Stromspeicher in Germany across Amazon, eBay, and AliExpress. It specifies the use case (price queries, offers) and distinguishes from sibling tool lookup_product by being a broad search tool.

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 tells when to use the tool: when a user asks about price, offer, 'günstig', 'wo kaufen', or a specific Stromspeicher. It mentions filtering options but does not explicitly state when not to use it or compare to alternatives beyond the sibling name.

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

All wospeicher.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

lookup_product and search_offers have clearly distinct purposes: one for retrieving a specific product by ID/URL, the other for searching and comparing offers across retailers. No overlap.

Naming Consistency5/5

Both tool names use snake_case with a consistent verb_noun pattern (lookup_product, search_offers). No mixing of conventions.

Tool Count3/5

With only 2 tools, the set feels thin for a price comparison service. While basic search and lookup are covered, more tools (e.g., filter, sort) would be expected for a richer experience.

Completeness3/5

The tools cover core search and lookup functionality but lack obvious operations like browsing categories, comparing multiple products, or filtering further. The search tool includes facets but no dedicated filter tool.

Resources

Need Help?