Skip to main content
Glama

watch.diy – DIY Store Finder

Find a product and its prices per chain

find_product
Read-onlyIdempotent

Searches watch.diy's index of DIY and garden products at German retailers (OBI, Bauhaus, toom, Hornbach, hagebau, Globus and more) by product name, EAN or manufacturer part number (MPN), and returns up to limit (1-5, default 3) products, best match first. Per product: name, brand, its EANs and per retailer the retailer's product name, its product page url and price with priceAsOf (when the price was read; a price older than 35 days is returned as null with priceNote). Only products the retailers sell themselves and still list online; store availability is not part of this answer: use where_to_buy_nearby with an EAN from here and a German postcode. Also returns match (ean, identifier, hybrid or text: how the query was answered) and a notice. When nothing matches, products is empty and message says what the index covers. Limits: public lookups are limited per client. Errors: invalid_request (names the field and the reason), quota_exceeded (with the minutes until it can be tried again), public_unavailable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoProducts to return, 1-5 (default 3)
queryYesProduct name or description (any language, typos tolerated), an EAN (8 or 13 digits) or a manufacturer part number (MPN)

Output Schema

NameRequiredDescriptionDefault
matchYesHow the query was answered: ean / identifier (exact), hybrid (full text + semantic), text (full text)
noticeYes
messageNoPresent when nothing was found
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses the freshness rule (prices older than 35 days come back null with priceNote), the catalogue restriction (only products retailers sell themselves and still list online), per-client rate limits, and named error codes with their payloads. This is behavior an agent could not derive from the structured fields.

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?

Front-loaded with purpose and match keys before the return shape, and every clause carries information. It is a single dense block with several chained clauses, which is slightly heavy but not padded.

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?

Even though an output schema exists, the description covers the no-match case, quota behavior, and the three error codes, which are the gaps that would otherwise force trial-and-error calls. Nothing an agent needs to invoke this correctly or interpret a failure is missing.

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 already 100%, but the description adds real meaning: query accepts any language with typos tolerated, and the match field explains how a lookup was resolved (ean, identifier, hybrid, text). Limit's default and range are repeated from the schema, so it is not purely additive.

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?

States a specific verb and resource ('Searches watch.diy's index of DIY and garden products at German retailers') and enumerates the matching keys (name, EAN, MPN), so the agent knows exactly what the tool resolves. It also names the sibling where_to_buy_nearby for the adjacent need, making the boundary unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly scopes out store availability ('store availability is not part of this answer') and routes to where_to_buy_nearby with the concrete recipe: an EAN from this result plus a German postcode. Coverage limits and the empty-result case are also spelled out, leaving no inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources