wovitamine.de Preisvergleich

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

search_offers

Read-onlyIdempotent

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

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. The description adds that it is read-only, mentions affiliate links with unchanged prices, and explains the 30-day price trend and response facets. It provides behavioral context beyond annotations, though it could mention data freshness or rate limits.

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 long but densely packed with useful information. It front-loads purpose and usage. The bilingual repetition (German and English) is somewhat redundant but acceptable. Overall, it earns its length.

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 presence of an output schema, the description does not need to explain return values. It still lists key fields (title, best price, brand, image, 30-day trend, attributes, links, facets), which is sufficient. No gaps are evident.

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%, so baseline is 3. The description adds minimal parameter context: an example for 'query' and that 'brand' must be an exact value from facets.marke. This is helpful but not substantial 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 explicitly states it finds the cheapest vitamins in Germany across Amazon, eBay, and AliExpress using specific verbs ('Findet', 'Preisvergleich'). It clearly distinguishes from the sibling tool 'lookup_product' by focusing on price comparison and multi-platform search.

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 this tool: when the user asks for price, offer, 'cheap', 'where to buy', or a specific vitamin supplement. It provides context about searching ~150 products with filters. However, it does not explicitly mention when not to use it or compare directly to the sibling 'lookup_product'.

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

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

The two tools have clearly distinct purposes: lookup_product retrieves details for a specific product, while search_offers finds products matching user criteria. No overlap.

Naming Consistency5/5

Both tools use a consistent verb_noun pattern (lookup_product, search_offers) with snake_case, making the naming predictable and clear.

Tool Count3/5

With only two tools, the server is minimal. While it covers the core search and lookup workflow, the scope feels limited for a price comparison domain that could benefit from additional tools like browsing categories or comparing products.

Completeness3/5

The tools cover the fundamental operations of searching for products and looking up details, but lack features like category listing, price history over custom periods, or product comparison, which are common in price comparison domains.

Resources

Need Help?