Skip to main content
Glama

Stofscout — Dutch Robot Vacuum Prices, Specs & Parts

Zoek robotstofzuigers

zoek_robotstofzuigers
Read-onlyIdempotent

Zoek en filter robotstofzuigers bij Nederlandse webwinkels op merk, prijs, zuigkracht (Pa), hoogte (cm), drempelhoogte (mm), geluid (dB), accuduur (min) of kenmerken (zelflegend, dweilfunctie, dweil wassen/drogen, lidar, wateraansluiting).

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

Input Schema

NameRequiredDescriptionDefault
merkNoMerknaam of slug, bijv. "roborock", "dreame", "ecovacs", "eufy".
lidarNoAlleen modellen met LiDAR-navigatie.
limietNoAantal resultaten (1-25, standaard 10).
sorteerNoSortering: "prijs" (laag naar hoog, standaard), "zuigkracht" (hoog naar laag) of "hoogte" (laag naar hoog).
zoektermNoVrije zoekterm op merk, modelnaam, EAN of artikelnummer.
max_prijsNoMaximale totaalprijs in EUR inclusief verzending (bijv. 400).
zelflegendNoAlleen modellen met zelflegend leegstation.
dweil_drogenNoAlleen modellen met gecontroleerde dweildroogfunctie in het station.
dweil_wassenNoAlleen modellen waarvan het station de dweil wast.
dweilfunctieNoAlleen modellen met dweilfunctie.
max_geluid_dbNoMaximaal opgegeven geluidsniveau in dB (bijv. 60).
max_hoogte_cmNoMaximale hoogte in cm (bijv. 8 of 9 voor onder een bank).
min_drempel_mmNoMinimale drempelhoogte in mm (bijv. 20 of 40).
min_accuduur_minNoMinimale opgegeven gebruiksduur in minuten (bijv. 180).
wateraansluitingNoAlleen modellen met vaste wateraansluiting.
min_zuigkracht_paNoMinimale opgegeven zuigkracht in Pa (bijv. 10000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world search. The description adds the meaningful scope detail that results come from Dutch web shops, but says nothing about result contents, pagination, or default behavior beyond what the schema already states.

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?

It is a single front-loaded sentence with no filler; the long attribute list is dense but every item maps to an actual parameter. Structure is efficient, though the parenthetical enumeration is slightly list-heavy.

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?

With 16 optional parameters and no output schema, the description should clarify what a result contains (prices, specs, shop, link) and whether results are ranked or paginated. It covers the input dimensions well but leaves the return side entirely unspecified.

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% and every filter named in the description (merk, prijs, zuigkracht, hoogte, drempelhoogte, geluid, accuduur, kenmerken) already has its own schema description with examples and units. The description therefore adds little semantic meaning beyond the schema.

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 specific verb and resource ('Zoek en filter robotstofzuigers bij Nederlandse webwinkels') and enumerates the filterable attributes, so the agent knows exactly what the tool retrieves. It does not explicitly distinguish itself from siblings such as model_details or vergelijk_modellen, which keeps it at 4 rather than 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 implied by 'zoek en filter' and the listed criteria, but there is no explicit statement of when to choose this over model_details, vergelijk_modellen, or aanbiedingen, and no exclusions or prerequisites are given.

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.