wopool.de Preisvergleich

Produkt auf wopool.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

Schlaegt ein konkretes Produkt im aktuellen wopool.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 wopool.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 and idempotentHint. The description adds that it returns best price, 30-day statistics, and offer link, which is beyond annotations. 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 contains both German and English versions of essentially the same information, leading to redundancy. It could be more concise by using one language.

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 low complexity (2 optional params, read-only) and presence of output schema, the description sufficiently covers what the tool does and returns. It is complete enough for an agent to use correctly.

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 parameter descriptions. The description adds the constraint 'exactly one of the fields' and clarifies the types of IDs (ASIN/externalId), adding value over schema.

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 verb 'looks up' and the specific resource 'product in the wopool.de catalog', and distinguishes it from the sibling 'search_offers' by specifying it is for a concrete product.

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', and the context of 'concrete product' implies when to use vs. the sibling for multiple offers. No explicit when-not-to-use mention, but adequate.

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

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

Disambiguation2/5

Both tools deal with product lookup and return similar information (best price, 30-day trend, links). An agent may find it unclear whether to use 'search_offers' for a specific ID or 'lookup_product' for a broad search, as the descriptions indicate overlap.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: 'lookup_product' and 'search_offers'. The naming is clear and predictable.

Tool Count3/5

With only 2 tools, the server is minimal. While it covers search and specific lookup, a price comparison service typically benefits from additional tools (e.g., category browsing, product comparison). The count feels slightly thin.

Completeness4/5

The tools cover the core use cases of searching for the cheapest price and looking up a specific product with price trends. Minor gaps exist, such as a lack of tools for browsing categories or viewing full price history beyond 30 days, but the surface is largely complete for a focused service.

Resources

Need Help?