Skip to main content
Glama

Stofscout — Dutch Robot Vacuum Prices, Specs & Parts

Nederlandse marktcijfers robotstofzuigers

marktcijfers
Read-onlyIdempotent

Haal de actuele Nederlandse robotstofzuiger-marktcijfers op (aantal leverbare modellen, laagste/mediaan/hoogste prijs, verdeling per prijsklasse, mediaan zuigkracht en prijsverschillen tussen winkels; CC BY 4.0).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety is covered. The description adds genuinely useful context beyond that: the data is current ("actuele") and is licensed CC BY 4.0, which flags an attribution obligation the agent may need to surface. It does not describe result shape or freshness granularity, which keeps it from a 5.

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?

One sentence, front-loaded with the action and resource, with the metric list and license placed in a parenthetical so the core claim reads first. It is dense but nothing is redundant; a slightly lighter metric list would scan faster.

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 input parameters and no output schema, the description carries the burden of saying what comes back, and it does so by enumerating the metric categories. What it lacks is any indication of the response's structure or whether the figures are bundled as one report, though for a parameterless read this is a minor gap.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could add or omit. It correctly describes the tool as parameterless by framing it as a single fetch of a fixed aggregate report.

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?

States a specific verb ("Haal ... op") and resource ("actuele Nederlandse robotstofzuiger-marktcijfers") and enumerates the aggregate metrics returned (model counts, min/median/max price, price-band distribution, median suction power, shop price differences). That enumeration implicitly separates it from model-level siblings like model_details and vergelijk_modellen, but no sibling is named explicitly.

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 it should call this for aggregate market statistics rather than per-model lookups, but there is no explicit when-to-use or when-not statement and no named alternative. The absence of parameters also means there is no guidance about scope filtering, which a caller might otherwise wonder about.

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.