Skip to main content
Glama

getecoback-raumklima

roboter_aufladung_fenster_mit_start_und_ende

Read-only

Vergleiche eine tatsächlich vollständige Aufladung ab niedrigem Akku mit dem Richtwert des exakten Dreame-Modells — Check completed charging evidence against the documented low-to-full reference

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": "<modell>",
      "start_niedrig": "<start_niedrig>",
      "ende_voll": "<ende_voll>",
      "beobachtete_minuten": "<beobachtete_minuten>",
      "unterbrechung": "<unterbrechung>",
      "gleiche_bedingungen": "<gleiche_bedingungen>"
    },
    "name": "roboter_aufladung_fenster_mit_start_und_ende"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
ende_vollYesVollständige Ladung laut Anzeige und Endzeit dokumentiert
start_niedrigYesBeginn bei ausdrücklich niedrigem Akku und Startzeit dokumentiert
unterbrechungYesEin zwischenzeitlicher Abbruch oder Verlassen der Station wurde beobachtet
beobachtete_minutenYesDauer dieses zusammenhängenden Versuchs in Minuten
gleiche_bedingungenYesTemperaturbereich laut passender Anleitung und keine abweichende Ladebedingung bekannt

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds that comparison is against a documented reference for the exact model, implying a closed reference table, but says nothing about tolerance, thresholds, or what the comparison result contains. With no output schema, that return-value gap is a real but moderate omission.

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?

Front-loaded with the core operation and kept to a single sentence pair. The German sentence is restated in English, which is mild duplication, but nothing is wasted and the key constraint (complete charge from low battery, exact model) comes first.

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?

The definition covers the required inputs well and the read-only nature is carried by annotations. However, for a comparison tool with no output schema, it never indicates what the comparison yields or how mismatches are reported, leaving an agent to call it without knowing the result shape.

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 all six required parameters documented, including enum meanings, so the baseline is 3. The description reinforces that 'start_niedrig' and 'ende_voll' must reflect genuinely documented evidence and that 'modell' must be the exact model, but adds no syntax or interpretation beyond the schema.

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 and resource: comparing an actually complete charge from low battery against the documented reference value for the exact Dreame model. That is clearly distinct from sibling tools about last documented charge, dock attempts, or resume behavior. It stops short of naming an alternative explicitly, but the operation is unambiguous.

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 phrase 'tatsächlich vollständige Aufladung ab niedrigem Akku' implies the precondition (a completed low-to-full charge with evidence), which gives an implicit when-to-use signal. There is no explicit when-not guidance, no mention of what to do with partial attempts, and no named alternative such as the last-documented-charge sibling.

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