Skip to main content
Glama

getecoback-raumklima

dreame_l10s_wasserstand_waschplatte_sichtbelege

Read-only

Priorisiere äußere Sichtbelege für einen ungewöhnlichen Wasserstand in der Waschplatte des L10s Ultra Gen 2 — Isolate documented abnormal washboard drainage observations

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_bestaetigt": "<modell_bestaetigt>",
      "wasserstand_auffaellig": "<wasserstand_auffaellig>",
      "tank_sitzt": "<tank_sitzt>",
      "ablauf_sichtbar_frei": "<ablauf_sichtbar_frei>",
      "loesung_freigegeben": "<loesung_freigegeben>"
    },
    "name": "dreame_l10s_wasserstand_waschplatte_sichtbelege"
  }
}

Input Schema

NameRequiredDescriptionDefault
tank_sitztYesSchmutzwassertank und zugängliche Dichtung sitzen laut Betriebsanleitung korrekt
modell_bestaetigtYesDreame L10s Ultra Gen 2 mit werkseitiger Tankstation auf dem Typenschild oder in den Unterlagen zum beobachteten Gerät bestätigt
loesung_freigegebenYesNur Wasser oder die für das Modell vom Hersteller zugelassene Lösung dokumentiert
ablauf_sichtbar_freiYesAn der entnehmbaren Waschplatte ist die laut Handbuch sichtbare Abflussstelle frei
wasserstand_auffaelligYesAbweichungen an der Waschplatte wurden laut Modellhinweis beobachtet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds some scope by emphasizing 'äußere Sichtbelege' and 'documented abnormal' observations, but it does not explain what the tool actually returns or how it processes the supplied evidence.

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?

The definition is compact and front-loads the domain context, with no filler or repetition. The dash-separated second clause is slightly abstract, but the overall structure is efficient.

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?

For a read-only tool with five required inputs and no output schema, the description should clarify what result the agent receives and how the evidence inputs produce that result. It instead remains abstract, leaving the operational outcome and return shape unclear.

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 five required parameters described and four using enums, so the schema carries the parameter semantics. The description itself adds no meaning about how those parameters are interpreted or combined.

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 identifies the domain (unusual water level in the L10s Ultra Gen 2 wash plate) and two abstract actions: prioritizing external visual evidence and isolating documented abnormal drainage observations. It does not clearly state whether the tool records, evaluates, or returns evidence, and it gives no sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'für einen ungewöhnlichen Wasserstand' implies the triggering condition, but there is no explicit when-to-use guidance, no exclusions, and no named alternative tool. The agent must infer the appropriate context from the domain wording alone.

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