Skip to main content
Glama
Sign In

wouhr.de Preisvergleich

by de.wouhr
OverviewDiscussionsAdmin

Kaufberatung & Vergleiche auf wouhr.de / buying guides

find_pages
Read-onlyIdempotent

Findet die passenden Seiten auf wouhr.de zu einer Frage rund um Uhren: Vergleichsseiten (z.B. nach Ausstattung oder Preisklasse), Ratgeber/Kaufberatung und Markenseiten – jeweils mit Titel, Kurzbeschreibung und Link. Ideal fuer "welcher Uhr ist gut fuer …", "worauf achten beim Kauf" oder "Modelle von ". EN: Finds matching pages on wouhr.de – comparisons, buying guides and brand pages with title, summary and link. Use for "which Uhr should I buy", "what to look for" or brand questions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoThema oder Frage / topic or question (optional).
languageNoSprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Antwortsprache / response language (de|en). Default: Accept-Language, sonst de."New value: +"Sprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en."
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "de",
-  "en"
-]New value: +[
+  "de",
+  "en",
+  "tr",
+  "ar",
+  "ru",
+  "pl",
+  "uk",
+  "fr",
+  "es",
+  "it",
+  "pt",
+  "nl",
+  "ro",
+  "el",
+  "hr",
+  "cs",
+  "hu",
+  "fa",
+  "zh",
+  "ja"
+]
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish readOnly, idempotent, non-destructive and closed-world behavior. The description adds that results include title, summary and link, plus the kinds of pages returned, but it does not disclose ranking, result limits or empty-query behavior.

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 core German description is front-loaded and specific, but the English version repeats the same information, effectively doubling the length. The bilingual duplication may serve multilingual users, yet it is not maximally concise for an agent-facing definition.

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?

For a read-only search tool with two documented parameters, no output schema and full annotation coverage, the description is largely complete. It explains the page types and the returned fields, though it omits result limits and ranking behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both the query and language parameters are already well documented in the schema. The description provides example query intents but adds no additional syntax or semantics beyond what the schema supplies.

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 states a specific verb and resource: it finds matching pages on wouhr.de, and it enumerates the page types (Vergleichsseiten, Ratgeber/Kaufberatung, Markenseiten). It implicitly separates itself from product/offer siblings by focusing on guide and comparison content, but it never names those siblings explicitly.

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 gives clear usage contexts with example questions such as "welcher Uhr ist gut fuer …", "worauf achten beim Kauf" and "Modelle von <Marke>". It does not state when not to use the tool or explicitly route the agent to lookup_product or 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 wouhr.de Preisvergleich toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources