wostrom.de Preisvergleich

Produkt auf wostrom.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

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

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description reinforces these by stating 'read-only' and listing output data. It adds context about the returned fields (best price, price statistics, link) 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 bilingual and contains two sentences covering both German and English. It is concise but could be slightly more streamlined by removing the repetition.

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 tool has an output schema (though not shown), the description adequately explains what the tool returns. It covers the parameters and usage constraint, making it complete for the agent.

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 clear descriptions for id and url. The description adds the constraint 'Exactly one of id/url must be given', which goes beyond the schema's optional parameters.

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 delivers best price, price statistics, and offer link. It distinguishes from sibling 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 mentions exactly one of id/url must be given but does not explicitly guide when to use this tool versus the sibling search_offers. Implicit understanding is that this is for specific product lookup, not searching.

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

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

Each tool has a distinct purpose: search_offers finds products by query, lookup_product retrieves details by ID/URL. No overlap.

Naming Consistency5/5

Both tools follow a clear verb_noun pattern (search_offers, lookup_product) with consistent snake_case.

Tool Count3/5

Two tools is on the lower end of appropriate for a price comparison server, but covers search and lookup. Could benefit from additional tools like category browsing.

Completeness3/5

The set covers core operations (search and lookup) but lacks features like filtering, comparison, or historical trends beyond 30 days.

Resources

Need Help?