Skip to main content
Glama

PrijsProfeet Nederland / Netherlands

Toon producten met foto

show_products
Read-onlyIdempotent

Producten bij de supermarkt voor een product- of merknaam (bijvoorbeeld 'oatly barista' of 'calvé pindakaas'), getoond als kaarten met foto, de prijs bij die supermarkt, de verpakkingsmaat en een link naar de productpagina. Verdeeld over de supermarkten, met de actieprijs en de prijs ervoor. De productnamen staan in de taal van die winkel, en de zoekfunctie vindt alleen woorden in die taal: Nederlands op www.prijsprofeet.nl en www.prijsprofeet.be ('peanut butter' heet daar 'pindakaas'), Duits op www.prijsprofeet.de ('peanut butter' heet daar 'Erdnussbutter'). Elk connectoradres hoort bij één land: www.prijsprofeet.nl geeft Nederlandse supermarkten, www.prijsprofeet.be Belgische en www.prijsprofeet.de Duitse. De gegevens zijn van PrijsProfeet, en de voorwaarden vragen bij elk gebruik een bronvermelding: PrijsProfeet met de url van elk genoemd product of merk. De prijzen worden elke nacht bijgewerkt, niet wekelijks, en de pagina toont de actuele stand.

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": "show_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesEen product- of merknaam, bijvoorbeeld 'oatly barista' of 'calvé pindakaas'. Een kale barcode levert hier geen producten maar een verwijzing naar de API: opvragen per barcode hoort bij een key.

Output Schema

NameRequiredDescriptionDefault
noticeNo
sourceYes
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantially more: prices refresh nightly rather than weekly, results are split across supermarkets, and use carries a contractual attribution obligation (PrijsProfeet plus the URL of each named product or brand). The language-restricted matching rule is also a behavioral constraint an agent cannot get from the schema.

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?

Front-loaded with the core function and the returned card contents, which is the right order. However, the language rule is stated and then restated in the same breath with the same peanut-butter examples, first for NL/BE and again for DE, and the domain-to-country mapping is repeated as a separate sentence. The 'niet wekelijks' clarification reads as defensive padding rather than information.

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 single-parameter read tool with an output schema and full annotation coverage, the description supplies the non-obvious essentials: query-language constraints, country/domain coupling, data freshness and the attribution requirement. The remaining gap is result-set behavior — no mention of any limit on how many products come back — which matters for an agent planning follow-up calls.

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% and the query parameter is already documented with examples, so the baseline would be 3. The description goes further by explaining that matching is lexical and language-bound — 'peanut butter' will not hit 'pindakaas' on the Dutch site or 'Erdnussbutter' on the German one — which directly shapes how an agent must phrase the query. It does not add syntax or format rules beyond that.

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?

Concrete verb-and-resource framing: it returns products for a product or brand name, shown as cards containing photo, that supermarket's price, package size and a link to the product page, grouped per supermarket with promo and prior price. That is far more specific than a restatement of the name. The only shortfall is that it never positions itself against the generic 'search' sibling, so an agent must infer that this is the product-lookup path.

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 real selection context: query language must match the store's language, and each connector domain maps to exactly one country (.nl Dutch, .be Belgian, .de German). It even carves out a case this tool does not serve — a bare barcode returns no products but a pointer to the key-gated API — which functions as an explicit when-not-to-use rule. Still missing is any statement about when to prefer 'search' or 'fetch' instead.

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