wouhr.de Preisvergleich

Produkt auf wouhr.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

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

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that the tool is read-only and returns specific data (best price, 30-day stats, offer link). No contradictions; the description enhances transparency 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 concise but includes both German and English versions, which may be redundant. Front-loads key information well. Slightly longer than necessary due to bilingual repetition, but still efficient.

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 simple nature (two optional parameters but exactly one required), high schema coverage, and presence of an output schema (not shown but mentioned), the description is complete. It covers all needed aspects for agent invocation.

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 descriptions for both parameters. The description adds clarity by stating 'exactly one of the fields id/url' and explaining the nature of each parameter (ASIN/ASIN extraction from URL). This goes beyond the schema alone.

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, returns best price, 30-day price stats, and offer link. It distinguishes itself from the sibling tool '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 specifies that exactly one of 'id' or 'url' must be provided, but does not explicitly state when to use this tool versus the sibling 'search_offers' or provide exclusion criteria. The context signals mention the sibling but the description lacks direct guidance.

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

All wouhr.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: search_offers is for broad searching/filtering of products, while lookup_product is for retrieving detailed info on a specific product by ID or URL. No ambiguity.

Naming Consistency5/5

Both tools use a consistent verb_noun snake_case pattern (search_offers, lookup_product), making them easy to distinguish and predict.

Tool Count3/5

With only two tools, the scope feels slightly limited for a price comparison server. While the tools are well-chosen, additional tools like category listing or trend analysis could be expected, making the count minimally appropriate.

Completeness3/5

The core functionality of searching and looking up products is covered, and facets provide some browsing capability. However, missing features like explicit category/label listing or multi-product comparison leave some gaps.

Resources

Need Help?