Skip to main content
Glama

getecoback-raumklima

saugroboter_buerstenpflege_erneut_gleiche_zone

Read-only

Vor einem unnötigen Bürstenkauf dokumentierte Nachkontrollen nach Pflege auf derselben Testfläche prüfen — Compare repeat observations before replacing a cleaned brush.

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": {
      "zugelassene_pflege_bestaetigt": "<zugelassene_pflege_bestaetigt>",
      "feste_stellen": "<feste_stellen>",
      "auffaellig_vorher": "<auffaellig_vorher>",
      "test_1": "<test_1>",
      "test_2": "<test_2>",
      "toleriert": "<toleriert>"
    },
    "name": "saugroboter_buerstenpflege_erneut_gleiche_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_1YesAuffällige Stellen im ersten vergleichbaren Lauf danach.
test_2YesAuffällige Stellen im zweiten vergleichbaren Lauf danach.
toleriertYesVor den Läufen selbst festgelegte Zahl auffälliger Stellen, die für die Aufgabe akzeptiert wird.
feste_stellenYesZahl festgelegter Stellen mit gleichem Prüfkriterium in allen Beobachtungen.
auffaellig_vorherYesAuffällige Stellen vor der Pflege.
zugelassene_pflege_bestaetigtYesWar die durchgeführte Pflege zulässig, das Teil passend und die Testfläche unverändert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful preconditions — the observations must be on the same test area and taken after care — but says nothing about what the comparison produces or how a verdict is reached, which matters for a decision-support tool.

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 definition is short, but it duplicates the same content in German and English and front-loads an odd purpose clause before the actual operation. The rationale and the action are fused into one long sentence, making it slower to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six required parameters and no output schema, the description should at least indicate what the tool returns or how the two measurements are judged against 'toleriert'. It leaves the decision logic and response shape unexplained, which is a real gap for a read-only comparison tool, though the annotations and full schema coverage limit the damage.

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 six parameters (including the boolean confirming permissible care) are already documented in the schema. The description only reinforces that test_1 and test_2 are comparable repeat runs on the same surface; it adds no semantics beyond that, so baseline 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 operation — comparing repeat follow-up observations (test_1 vs test_2) on the same test area after brush care, in service of deciding on a brush replacement. The verb/resource pairing is identifiable, though the German clause is syntactically convoluted and reads partly as rationale rather than function. It does not explicitly distinguish itself from the many sibling saugroboter_* tools.

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 context is implied by the framing 'before an unnecessary brush purchase' and the constraint 'after care on the same test area', so an agent can infer when the tool applies. However, no alternative is named, no exclusion is stated, and no prerequisite (e.g. that two comparable post-care runs must already exist) is spelled out beyond the phrase 'documented follow-up checks'.

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