wotablet.de Preisvergleich

Produkt auf wotablet.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

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

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior. Description adds value by specifying output details and input constraint (exactly one parameter). No contradictions. No mention of auth or rate limits, but annotations suffice.

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?

Bilingual but each sentence is purposeful: purpose, output, constraint. No fluff. Could be slightly shorter by using one language, but negligible.

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?

With only 2 optional parameters (but exactly one required), rich annotations, and an output schema, the description covers purpose, constraints, and output. No major gaps.

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 each parameter. The description in the tool definition reinforces the 'exactly one' rule, which is not in the schema. This adds important usage constraint beyond the 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?

Description uses specific verb ('looks up'/'schlaegt nach'), identifies exact resource ('Produkt im wotablet.de-Katalog'), and distinguishes from sibling 'search_offers' by focusing on ID/URL lookup. It also lists specific output fields (Bestpreis, 30-Tage-Preisstatistik, Angebots-Link).

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?

States that exactly one of 'id' or 'url' must be provided, and hints at using 'search_offers' to obtain externalId. However, it does not explicitly state when NOT to use this tool (e.g., for broad queries, use search_offers instead).

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

All wotablet.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 serve clearly distinct purposes: search_offers for querying the catalog with filters, and lookup_product for retrieving details of a specific product by ID or URL. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools use a consistent verb_noun pattern with underscores (search_offers, lookup_product), making their actions predictable and clear.

Tool Count4/5

With 2 tools for a price comparison service, the set is slightly minimal but still functional. The search tool includes facets that reduce the need for additional browsing tools, so the count is acceptable.

Completeness4/5

The tools cover search and detail lookup, which are the core operations. Minor gaps exist, such as the lack of a dedicated tool for listing brands or comparing multiple products, but these are partially addressed by facets in search_offers.

Resources

Need Help?