Skip to main content
Glama

PrijsProfeet België / Belgique

Details van een merk of product

fetch
Read-onlyIdempotent

De details van een zoekresultaat, op zijn id. Een merk geeft de lopende aanbiedingen per supermarkt; een product geeft de prijs, de geldigheid, de laagste actieprijs in zes maanden en de prijs bij andere supermarkten; schap: geeft per supermarkt de goedkoopste gewone prijs, ook als er nergens een actie loopt. Altijd met de link naar de pagina.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description is not required to restate it. It does add genuine behavioral context by saying the returned payload varies by id type and that a page link is always included. The only gap is error behavior for an unknown or malformed id.

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?

Content is front-loaded with the core operation, then the id-variant detail, then the always-included page link. It is a single dense sentence chain using semicolons, which is efficient but makes the per-id-type payoff slightly harder to scan than a short list would be.

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?

With an output schema present the description does not need to enumerate return fields, yet it usefully flags what differs per id type, and the annotations cover safety and idempotency. For a one-parameter lookup tool this is nearly complete; only failure behavior for an invalid id is unaddressed.

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 description coverage is 0% for the single `id` parameter, so the description has to carry that meaning and largely does: it distinguishes brand ids, product ids and `schap:`-prefixed ids and explains what each variant resolves to. It stops short of stating whether the id must come verbatim from `search` results or what format a brand/product id takes.

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 states a concrete operation on a concrete resource: it returns the details of a search result identified by its `id`. It also enumerates what each id type yields (brand → running offers per supermarket; product → price, validity, six-month lowest promotional price, other supermarkets' prices; `schap:` → cheapest regular price per supermarket). An agent can tell this is the detail-lookup counterpart to `search` without opening either schema.

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?

The phrase 'van een zoekresultaat' ties the call to ids obtained from `search`, and the id-prefix explanation (`schap:`) gives real guidance about what can be passed. What is missing is an explicit statement of when *not* to use it or a named pointer back to `search` as the way to obtain an id; the usage context is clear but not framed as a rule.

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