Skip to main content
Glama

getecoback-raumklima

poolroboter_umkehrabweichung_beckenvariante_beleg

Read-only

Eigene Laufnotizen nach einem Wechsel von Beckenoberfläche oder freigegebener Zone gegeneinander abgrenzen — Mark exactly which prior pool observations need retesting.

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": {
      "modell_gleich": "<modell_gleich>",
      "bodenoberflaeche_gleich": "<bodenoberflaeche_gleich>",
      "wandoberflaeche_gleich": "<wandoberflaeche_gleich>",
      "treppenform_gleich": "<treppenform_gleich>",
      "vergleichbare_betriebsbedingungen": "<vergleichbare_betriebsbedingungen>"
    },
    "name": "poolroboter_umkehrabweichung_beckenvariante_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
modell_gleichYesGenaues Robotermodell blieb gleich?
treppenform_gleichYesGeometrie der bezeichneten Treppenzone unverändert?
wandoberflaeche_gleichYesBetrachtete Wandoberfläche unverändert?
bodenoberflaeche_gleichYesOberfläche des betrachteten Bodens unverändert?
vergleichbare_betriebsbedingungenYesBetriebsbedingungen, freigegebene Nutzung und Beobachtbarkeit für die jeweilige Zone bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/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. Beyond that the description adds almost nothing: it does not explain how the five booleans combine, what happens if one is false, or whether the tool records, rejects, or merely reports. The phrase 'Mark exactly which prior pool observations need retesting' hints at a write-like marking action that is not explained relative to the read-only annotation.

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?

It is short, but the German clause and the English clause say essentially the same thing, so half the text is redundant. The front-loaded portion ('Eigene Laufnotizen nach einem Wechsel ...') does not orient the agent before the vague second half.

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

Completeness2/5

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

With five required booleans and no output schema, the description should explain what the boolean combination yields and what an agent should do with the result. Instead it leaves the outcome undefined and gives no indication of what 'retesting' means in practice.

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 each of the five booleans is already documented in the input schema. The description contributes no additional meaning per parameter — no explanation of which observation set is being judged or how 'vergleichbare_betriebsbedingungen' gates the others. Baseline 3 applies when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a domain concept ('Laufnotizen ... gegeneinander abgrenzen') and a trigger ('Wechsel von Beckenoberfläche oder freigegebener Zone'), but it never states plainly that the tool validates comparability of prior observations via five yes/no confirmations. The mixed German/English phrasing restates the same idea twice without converging on a concrete verb+resource, so an agent must open the schema to understand what is actually produced.

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?

A usage condition is implied: call this after a change of pool surface or released zone to determine which earlier observations still hold. However, there is no explicit when-not guidance, no prerequisites, and no reference to sibling tools such as poolroboter_beckencheck or poolroboter_treppenumkehr_sichtprotokoll that might overlap.

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