Skip to main content
Glama

Stofscout — Dutch Robot Vacuum Prices, Specs & Parts

Passende onderdelen per model

zoek_onderdelen
Read-onlyIdempotent

Vind gecontroleerde passende onderdelen (stofzakken, filters, hoofdborstels, zijborstels, dweildoeken, onderhoudssets) en prijzen per stuk voor een robotstofzuiger.

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": {
      "slug": "<slug>"
    },
    "name": "zoek_onderdelen"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesModel-slug op stofscout.nl, bijv. "roborock-q7-max".
soortNoOptioneel filter op soort onderdeel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a safe, read-only, idempotent, closed-world lookup. The description adds useful context that results are 'gecontroleerde' compatible parts and include per-piece prices, but it does not cover return shape, empty results, price currency, or other behavioral details beyond the annotations.

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?

The description is a single front-loaded sentence with no wasted wording. It efficiently states the resource, compatibility guarantee, categories, and price inclusion.

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 simple two-parameter read-only lookup with full schema descriptions and clear annotations, the description covers what the tool finds and that prices are included. It could be more complete with explicit usage guidance or return constraints, but nothing essential is missing for invocation.

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 the slug and optional soort filter are already well documented. The description reinforces the per-model scope and lists part categories, but it adds little parameter-level meaning beyond the schema, and its 'onderhoudssets' wording differs slightly from the enum value 'sets'.

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 states a specific verb and resource: finding verified compatible parts and per-piece prices for a robot vacuum, with concrete part categories. It does not explicitly distinguish itself from sibling tools such as model_details or aanbiedingen, so it is clear but lacks direct sibling differentiation.

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 'per model' and the required slug parameter, indicating this is for retrieving parts for a known vacuum model. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives for parts versus models, deals, or comparisons.

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.