Skip to main content
Glama

getecoback-climate-weather

saugroboter_ergebnis_stichprobe

Read-only

Einfachen und doppelten Reinigungslauf mit derselben Stichprobenmethode vergleichen — Compare residual dirt after one versus two passes using equivalent checks.

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": {
      "sample_points": "<sample_points>",
      "residue_one": "<residue_one>",
      "residue_two": "<residue_two>",
      "comparable": "<comparable>"
    },
    "name": "saugroboter_ergebnis_stichprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
comparableYesGleiche Fläche, gleichartige Anfangsverschmutzung und gleiche Bewertungskriterien?
residue_oneYesPunkte mit sichtbaren Rückständen nach einem Lauf.
residue_twoYesPunkte mit sichtbaren Rückständen nach zwei Läufen.
sample_pointsYesGleiche Anzahl an Stichprobenpunkten je Variante. Jeder Punkt zählt einmal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioural constraint, namely that both variants must be evaluated with equivalent checks and the same sampling method. It does not say what the comparison returns or how non-comparable inputs are handled, and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core comparison, but it states the same thing twice in German and English. The English half adds only the phrase 'equivalent checks', so much of the text does not earn its place. The duplication is not harmful, but it is redundant.

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?

This is a simple read-only computation over four fully documented scalar parameters, and the description's scope matches that complexity. Because there is no output schema, the only remaining gap is that the shape of the comparison result is never described.

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 all four parameters, including the comparable flag and the one- and two-pass residue counts, are already fully documented in the schema. The description only reinforces the notion of equivalent checks and adds no format, unit, or edge-case detail beyond that. The baseline of 3 applies.

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 names a specific verb and object: compare residual dirt after one versus two cleaning passes. That is clearly distinct from neighbouring sampling tools such as trockner_ende_feuchte_stichprobe. There is no explicit naming of a sibling tool that it should not be confused with, so it stops just short of 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?

The use case is implied rather than stated: an agent can infer that the tool is for A/B comparison of one versus two passes. There is no guidance on when not to use it, no statement of prerequisites, and no mention of what to do when the runs are not comparable.

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.

Resources