wovitamine.de Preisvergleich

Produkt auf wovitamine.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

Schlaegt ein konkretes Produkt im aktuellen wovitamine.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 wovitamine.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).

Input Schema

TableJSON 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

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

Behavior3/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 returns best price and statistics but does not go beyond what annotations provide for behavioral traits. 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 bilingual with some redundancy (German and English say similar things). It could be more concise by keeping only one language. The structure is functional but not optimized.

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 (not shown), the description sufficiently covers purpose, parameters, exclusivity, and return value hints. It does not need to detail return structure.

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 the description adds the key constraint that exactly one of 'id' or 'url' must be given, which is not in the schema. It also clarifies that 'id' is ASIN/externalId and 'url' extracts the ASIN.

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, returning best price, 30-day price statistics, and offer link. It distinguishes itself from the sibling tool 'search_offers' by specifying a concrete lookup rather than a 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?

It explicitly specifies that exactly one of 'id' or 'url' must be provided, and describes the URL format. It implies use when you have a specific product identifier, but does not explicitly compare with the sibling tool or state when not to use.

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?