Skip to main content
Glama

Stofscout — Dutch Robot Vacuum Prices, Specs & Parts

Modeldetails en winkelprijzen

model_details
Read-onlyIdempotent

Haal actuele winkelprijzen (incl. verzending en levertijd), 90-dagen deal-check, gecontroleerde specificaties met fabrikantbron, handleiding-pdf en aantal passende onderdelen op voor één robotstofzuiger.

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

Input Schema

NameRequiredDescriptionDefault
slugNoModel-slug op stofscout.nl, bijv. "roborock-q7-max" of "dreame-l40-ultra".
zoektermNoAlternatief als de exacte slug onbekend is, bijv. "Roborock Qrevo S".

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 this a safe, idempotent, closed-world read, so the safety bar is covered. The description adds genuine value beyond that by disclosing what the response contains — price including shipping and delivery time, a 90-day deal history check, manufacturer-sourced specifications, a manual PDF, and a matching-parts count. It does not say what happens on an unknown slug or an ambiguous zoekterm, which keeps it at 4.

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?

A single sentence that front-loads the most-requested output (current prices) and then layers the secondary payloads. Dense but every clause names a distinct returned artifact, so little is wasted; the parenthetical nesting makes it slightly harder to scan.

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 no output schema, the description must carry the return-value burden, and it does so by enumerating five distinct data facets the agent will receive. What remains unstated is error/ambiguity behavior and whether both parameters are optional in practice (required count is 0), which is a modest gap rather than a blocking one.

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 both parameters (slug with concrete examples, zoekterm as the fallback) are already fully documented, establishing a baseline of 3. The description adds no further semantics about how the two interact or which wins when both are supplied.

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 pairs a concrete verb ("Haal") with a specific resource and scope: shop prices plus a bundle of per-model data for exactly one robot vacuum. The enumerated payload facets (prices including shipping/delivery, 90-day deal check, manufacturer-sourced specs, manual PDF, matching parts count) make it distinguishable from siblings like aanbiedingen or marktcijfers. It stops short of naming a sibling to route against, so a 4 rather than 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: the phrase "voor één robotstofzuiger" signals a single-model detail lookup, and the schema's slug/zoekterm pair hints at the two lookup paths. There is no explicit statement of when to prefer this over 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.