Skip to main content
Glama

getecoback-raumklima

saros10r_trocknung_luftauslass_und_modus

Read-only

Trenne einen tatsächlich angezeigten Dock-Trocknungslauf von einer bloß erwarteten Automatik und einem verdeckten Luftauslass — Check recorded Saros drying mode and outlet condition separately

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>",
      "automatik_freigegeben": "<automatik_freigegeben>",
      "trocknung_erfasst": "<trocknung_erfasst>",
      "auslass_offen": "<auslass_offen>"
    },
    "name": "saros10r_trocknung_luftauslass_und_modus"
  }
}

Input Schema

NameRequiredDescriptionDefault
auslass_offenYesTrocknungs-Luftauslass war von außen gesehen frei
modell_bestaetigtYesSaros 10R mit Tankstation auf dem Typenschild oder in den Unterlagen zum beobachteten Gerät bestätigt
trocknung_erfasstYesDock-Trocknung für denselben Zeitraum in Status oder App beobachtet
automatik_freigegebenYesAutomatisch Trocknen war für die betrachtete Zeit aktiviert

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 genuinely useful semantics beyond that — that expected automation is not the same as recorded drying, and that a covered outlet is a third independent condition — but it omits the return shape and whether conflicting parameter combinations are rejected or merely reported.

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?

A single clause chain with the disambiguation front-loaded, followed by a compact English restatement that costs little and helps non-German readers. The bilingual duplication is mild redundancy but nothing is padded or buried.

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?

Four required parameters, three of them enums, and no output schema — so the description carries the burden of explaining the result, which it does not do. An agent knows what to supply and the spirit of the check, but not what comes back or how the 'offen' values are resolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns an increment by naming the three concepts the parameters encode (angezeigter Lauf, erwartete Automatik, verdeckter Luftauslass) and stressing they are recorded separately, which explains why all four are independently required. It does not clarify the third enum value 'offen' versus 'nein', which is the main residual ambiguity.

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 English gloss gives a verb and resource ('Check recorded Saros drying mode and outlet condition'), and the German clause sharpens it to separating an actually-shown drying run from an expected automation and a concealed outlet. However, it never states what the tool actually produces — an assessment, a classification flag, or a status record — so the purpose stays at the level of 'distinguish these three things' rather than 'does X and returns Y'.

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 is only implied: use it when the observed drying state must be told apart from assumed automation, which is a real situational cue. There is no explicit when-not, no prerequisite statement, and no naming of an alternative (e.g. the sibling saros10r_filter_trocknungsfenster or saros10r_pausenzeit_und_schlafzustand) that would tell an agent which check to pick.

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