wospeicher.de Preisvergleich

Produkt auf wospeicher.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

Schlaegt ein konkretes Produkt im aktuellen wospeicher.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 wospeicher.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.1/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 concrete return values (best price, 30-day stats, offer link) and confirms the read-only nature. 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.

Conciseness5/5

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

The description is concise with two bilingual sentences plus a clear constraint. No redundancy or wasted words.

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 output schema exists, the description sufficiently covers inputs, returns, and constraints. No significant missing context for a read-only lookup tool.

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%, baseline 3. The description adds meaning by explaining the 'id' as ASIN/externalId and 'url' as an Amazon product URL, plus the constraint to provide exactly one.

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 it looks up a specific product by ID or URL and returns best price, statistics, and link. It distinguishes from the sibling 'search_offers' by the precise lookup mechanism, though not explicitly contrasting.

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 mandates exactly one of 'id' or 'url' must be provided ('Genau eines der Felder'), and specifies what the tool returns. It does not explicitly contrast with 'search_offers' but the context implies use when a specific identifier is known.

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

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

lookup_product and search_offers have clearly distinct purposes: one for retrieving a specific product by ID/URL, the other for searching and comparing offers across retailers. No overlap.

Naming Consistency5/5

Both tool names use snake_case with a consistent verb_noun pattern (lookup_product, search_offers). No mixing of conventions.

Tool Count3/5

With only 2 tools, the set feels thin for a price comparison service. While basic search and lookup are covered, more tools (e.g., filter, sort) would be expected for a richer experience.

Completeness3/5

The tools cover core search and lookup functionality but lack obvious operations like browsing categories, comparing multiple products, or filtering further. The search tool includes facets but no dedicated filter tool.

Resources

Need Help?