Skip to main content
Glama
Sign In

wosneaker.de Preisvergleich

by de.wosneaker
OverviewDiscussionsAdmin

Kaufberatung & Vergleiche auf wosneaker.de / buying guides

find_pages
Read-onlyIdempotent

Findet die passenden Seiten auf wosneaker.de zu einer Frage rund um Sneaker: Vergleichsseiten (z.B. nach Ausstattung oder Preisklasse), Ratgeber/Kaufberatung und Markenseiten – jeweils mit Titel, Kurzbeschreibung und Link. Ideal fuer "welcher Sneaker ist gut fuer …", "worauf achten beim Kauf" oder "Modelle von ". EN: Finds matching pages on wosneaker.de – comparisons, buying guides and brand pages with title, summary and link. Use for "which Sneaker 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety and scope are covered structurally. The description adds the return shape (title, summary, link) but says nothing about result limits, ranking or permission requirements beyond that.

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 core purpose, result format and usage examples are front-loaded and easy to scan. The fully bilingual duplication is defensible for a multilingual domain but makes it longer than strictly necessary.

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 two-parameter read-only search, the description covers what the tool does, when to use it and what fields come back, while annotations cover safety. Only secondary details such as result ordering or limits are absent, which is acceptable for this complexity.

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 description coverage is 100%: both the query and language parameters are fully documented in the schema, including defaults and fallback behavior. The description adds no parameter-level detail beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb ('Findet') and resource ('Seiten auf wosneaker.de') and enumerates what kinds of pages are returned (comparisons, buying guides, brand pages). It implies a distinction from product/offer search via the content types, but never names the siblings to make the boundary 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?

Gives concrete example question shapes ('welcher Sneaker ist gut für …', 'worauf achten beim Kauf', 'Modelle von <Marke>') that map directly to when this tool is the right call. It stops short of stating when not to use it or naming alternatives like lookup_product or search_offers.

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

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