Skip to main content
Glama

Stofscout — Dutch Robot Vacuum Prices, Specs & Parts

Vergelijk twee modellen

vergelijk_modellen
Read-onlyIdempotent

Vergelijk twee robotstofzuigers naast elkaar op actuele prijs, prijsverschil, winkels op voorraad en verschillen in gecontroleerde specificaties.

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_a": "<slug_a>",
      "slug_b": "<slug_b>"
    },
    "name": "vergelijk_modellen"
  }
}

Input Schema

NameRequiredDescriptionDefault
slug_aYesSlug of naam van het eerste model.
slug_bYesSlug of naam van het tweede model.

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 the safety profile is covered. The description still adds value beyond them by disclosing what the result contains – current price, price difference, in-stock stores, and differences in verified specifications – which is important since there is no output schema.

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 sentence that front-loads the two-model comparison and then lists the returned dimensions with no filler or repetition. Every clause carries information.

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 two-string, read-only tool with full schema coverage and rich annotations, the description covers purpose and result content sufficiently. Minor gaps remain around the slug format and behaviour on an invalid or unknown slug.

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%, with both slug_a and slug_b documented as 'Slug of naam van het eerste/tweede model', so the baseline is 3. The description adds no format detail (slug syntax, whether names are accepted, what happens with an unknown slug) beyond what the schema already says.

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 (vergelijk) plus the resource (twee robotstofzuigers) and enumerates the comparison axes: actuele prijs, prijsverschil, winkels op voorraad, en verschillen in gecontroleerde specificaties. An agent can tell it is a two-model, side-by-side comparison. It stops short of naming or contrasting sibling tools such as model_details, so it does not reach 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 implied by the wording 'twee ... naast elkaar' – it is the tool to reach for when two models must be compared. There is no explicit statement about when not to use it, nor a pointer to single-model or listing siblings for other needs. Adequate but leaves routing to inference.

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.