wosolar.de Preisvergleich

Produkt auf wosolar.de per ID/URL nachschlagen

lookup_product

Read-onlyIdempotent

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

Behavior4/5

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

The description adds that the tool is read-only (consistent with annotations) and describes the output data. Annotations already declare readOnlyHint and idempotentHint, so the description provides additional context on return values without contradicting 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 concise and front-loads the core purpose. It uses two short sentences in both German and English, which is slightly redundant but still efficient. No unnecessary details.

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 (not shown but mentioned), the description covers purpose, parameters, usage constraints, and return values adequately. It also references the sibling tool search_offers, making the context complete for an 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?

While the input schema already has 100% coverage, the description adds crucial usage constraints (exactly one field) and clarifies the meaning of 'id' (link to externalId from search_offers) and 'url' (Amazon product URL with ASIN extraction), surpassing the schema's description.

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 that the tool looks up a specific product by ID or URL, specifies the returned data (best price, statistics, link), and distinguishes itself from the sibling tool 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly specifies that exactly one of 'id' or 'url' must be provided, and explains the sources for 'id' (ASIN or externalId from search_offers). While it doesn't explicitly state when not to use, the context (sibling tool) implies it's for specific lookup, not listing.

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

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

Disambiguation5/5

The two tools have clearly distinct purposes: search_offers finds products based on search criteria, while lookup_product retrieves detailed price statistics and links for a specific product ID. There is no ambiguity or overlap.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern using lowercase with underscores (search_offers, lookup_product). The naming is predictable and clear.

Tool Count4/5

With only two tools, the server is slightly below the typical 3-15 range, but the pair covers the essential search-and-lookup workflow for a price comparison domain. Each tool earns its place, though a few more tools (e.g., for product categories or comparison) could be expected.

Completeness5/5

The tool surface covers the full lifecycle needed: users can search for products with filters and facets, then look up detailed price information for a specific product. There are no obvious gaps, and the workflow is complete for the stated purpose of price comparison.

Resources

Need Help?