wohandy.de Preisvergleich

Produkt auf wohandy.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

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

Behavior5/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description confirms 'read-only' and adds detail about returned data (best price, statistics, link), providing complete behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is concise, two sentences, front-loading key information in German and English. Every sentence adds value without redundancy.

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 presence of an output schema and annotations, the description fully covers purpose, parameter constraints, and return value highlights. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions (100% coverage). Description adds critical constraint that exactly one must be provided and clarifies that URL is an Amazon product link with ASIN extraction.

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 and returns best price, 30-day statistics, and offer link. It distinguishes from the sibling tool 'search_offers' which is for searching multiple products.

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 requires exactly one of id or url to be provided. It implies usage when a specific product identifier is known, but could be more explicit about when not to use it vs. search_offers.

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

All wohandy.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.6/5.0

Disambiguation5/5

The two tools have clearly distinct purposes. 'search_offers' finds products based on search criteria, while 'lookup_product' retrieves details for a specific product by ID or URL. No overlap.

Naming Consistency5/5

Both tools use consistent snake_case naming convention ('lookup_product', 'search_offers'), following a clear verb_noun pattern.

Tool Count4/5

The server has only two tools, but they cover the core functionality of searching and looking up products. While minimal, it is appropriate for a focused price comparison server.

Completeness5/5

The tool surface is complete for the server's read-only purpose: search for products and look up details. No obvious missing operations given the domain.

Resources

Need Help?