Skip to main content
Glama

Stofscout — Dutch Robot Vacuum Prices, Specs & Parts

Aanbiedingen van vandaag

aanbiedingen
Read-onlyIdempotent

Haal de gecontroleerde aanbiedingen en echte prijsdalingen van vandaag op bij Nederlandse webwinkels (vergeleken met eerdere meetdagen of een tweede winkel).

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

Input Schema

NameRequiredDescriptionDefault
merkNoOptioneel filter op merknaam of slug.
limietNoAantal resultaten (1-25, standaard 10).
max_prijsNoMaximale prijs in EUR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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. The description adds genuinely non-structured context: results are 'gecontroleerd' and restricted to 'echte prijsdalingen', defined as drops verified against prior measurement days or a second shop — that tells the agent how noisy or trustworthy the output is. It still says nothing about result volume, ordering, or freshness beyond 'vandaag'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb first and the scoping qualifiers after; nothing is redundant and every clause (today, Dutch shops, verified, comparison basis) carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-optional-parameter read tool with full annotation coverage this is close to sufficient, but with no output schema the description never indicates what a deal record contains (price, shop, reference price, discount) or how results are ordered and capped, leaving the return shape to inference.

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%, so all three optional parameters (merk, limiet, max_prijs) are already fully documented in the schema. The description contributes no extra parameter meaning — no interaction rules (e.g. how max_prijs relates to the price-drop definition) and no default behaviour notes beyond what the schema states. 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?

The description gives a concrete verb-plus-resource ('Haal de gecontroleerde aanbiedingen en echte prijsdalingen van vandaag op') scoped to Dutch webshops, plus the qualifying notion of comparison against earlier measurement days or a second shop. That makes the resource distinguishable from generic catalog-search siblings, but it never names or contrasts an alternative tool, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for current deals and price drops, but there is no explicit statement of when to prefer it over the sibling tools or when it is not appropriate. No prerequisites, no exclusions, no routing hints.

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.