wosneaker.de Preisvergleich

Produkt auf wosneaker.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

Schlaegt ein konkretes Produkt im aktuellen wosneaker.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 wosneaker.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

A3.7/5.0

Behavior4/5

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

The description reveals what the tool returns (best price, 30-day stats, offer link) and confirms read-only behavior, aligning with annotations. It adds context beyond annotations by detailing the output scope.

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 and to the point, with both German and English versions provided. Key information is front-loaded, and there is no redundant text.

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 existence of an output schema, the description sufficiently covers inputs and the nature of the output. It mentions the key result components, making it complete for a lookup tool.

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?

The schema covers both parameters with descriptions. The description reiterates the constraint of using exactly one and clarifies that the URL is used for ASIN extraction, adding minimal extra meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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. It mentions the input sources (ASIN/externalId from search_offers) and distinguishes from sibling search_offers by targeting a single product.

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, which is a key usage constraint. However, it does not explicitly state when to use this tool versus the sibling 'search_offers' tool, though the intent is implied.

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

All wosneaker.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 a specific product by ID/URL, while search_offers performs an open-ended search across the catalog. No overlap in functionality.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern using snake_case (lookup_product, search_offers), making the naming predictable and intuitive.

Tool Count4/5

With only 2 tools, the server is quite minimal. However, for a focused price comparison service covering search and specific product lookup, the count is acceptable, though additional features like category browsing might be expected.

Completeness4/5

The tool set covers the core workflows: searching for offers and looking up specific products. However, there are minor gaps such as no tool for listing brands, categories, or comparing multiple products, which could improve completeness.

Resources

Need Help?