wolaptop.de Preisvergleich

Produkt auf wolaptop.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that the operation is read-only and mentions returned data (best price, 30-day stats, offer link), which is consistent and adds value.

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 somewhat lengthy due to bilingual text (German and English), but the key information is front-loaded and each sentence adds value. Could be slightly more concise.

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 captures essential behavioral and usage details. It covers what the tool does, its inputs, and outputs, making it complete for a simple lookup tool.

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?

The schema already describes both parameters (id and url). The description adds that exactly one field must be used and explains that externalId comes from search_offers, enhancing understanding beyond schema definitions.

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 specifies the tool looks up a product by ID or Amazon URL, and distinguishes it from the sibling tool 'search_offers' which is likely a broader search. The verb 'look up' and resource 'product' are explicit.

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 states that exactly one of 'id' or 'url' must be provided, which is a clear usage rule. However, it does not explicitly say when to use this tool over the sibling 'search_offers' or mention exclusions, though the context implies it.

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

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

Disambiguation5/5

The two tools have clearly distinct purposes: search_offers performs broad searches for laptops with multiple filters, while lookup_product retrieves details for a specific product by ID or URL. There is no overlap in functionality.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern using snake_case: 'lookup_product' and 'search_offers'. This makes the action and target immediately clear.

Tool Count3/5

With only two tools, the server is minimal but functional for basic price comparison. The tools cover search and detail lookup, which is reasonable for a focused domain, though additional tools like category listing or price history could enhance completeness.

Completeness4/5

The server covers the essential workflows: finding products by search and retrieving detailed price info for a specific product. Minor gaps like lacking a tool to compare multiple products or view trending items, but core operations are present.

Resources

Need Help?