Skip to main content
Glama

getecoback-climate-weather

tfa_305055_komfortstatus_rohdaten_getrennt

Read-only

Erhalte beim TFA 30.5055.01 die Feuchterohwerte, wenn Komfortmodi wechseln — Preserve raw humidity comparison when the TFA comfort mode changes

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_30505501": "<modell_30505501>",
      "modus_a": "<modus_a>",
      "modus_b": "<modus_b>",
      "rh_a": "<rh_a>",
      "rh_b": "<rh_b>",
      "ort_und_temperatur_passend": "<ort_und_temperatur_passend>"
    },
    "name": "tfa_305055_komfortstatus_rohdaten_getrennt"
  }
}

Input Schema

NameRequiredDescriptionDefault
rh_aYesFeuchteanzeige der ersten Ablesung in Prozent
rh_bYesFeuchteanzeige der zweiten Ablesung in Prozent
modus_aYesErster Komfortmodus
modus_bYesZweiter Komfortmodus
modell_30505501YesDasselbe Gerät 30.5055.01 für beide Ablesungen eindeutig dokumentiert
ort_und_temperatur_passendYesMessort, Zeitbezug und Temperaturvergleich sind dokumentiert

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. The description adds that the tool preserves a raw comparison (non-destructive capture), but it never explains why "ort_und_temperatur_passend" and "modell_30505501" are hard gates or what happens when they are false, which is the real behavioral risk here.

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?

Two short, front-loaded clauses with the resource and trigger stated immediately, and the English half is a near-mirror of the German. The bilingual duplication costs a little space but is not wasteful given the mixed-language audience.

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, an all-or-nothing validation gate and no output schema, the description should say what is actually returned (raw pair, delta, verdict) and how the gate booleans behave. It is adequate to call the tool but leaves the return shape and gating behavior unspecified.

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 coverage is 100% with enums for the two mode parameters and bounded percentages, so the schema carries the parameter burden. The description contributes only the framing that rh_a/modus_a and rh_b/modus_b form a before/after comparison; it adds no format or validation semantics beyond the schema baseline.

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?

Names a specific verb ("Erhalte") and a specific resource ("Feuchterohwerte") scoped to a named device (TFA 30.5055.01) and a trigger condition (comfort mode change). An agent can tell it captures raw humidity values across a mode switch, though it does not distinguish itself from any sibling.

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 trigger condition "wenn Komfortmodi wechseln" implies when the tool applies, but there is no explicit when-not guidance, no prerequisites, and no named alternative for related humidity/comfort tasks. Usage must be inferred from the trigger clause 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