Skip to main content
Glama

getecoback-climate-weather

thermostat_punktwaerme_offset_moduswechsel

Read-only

Den Fühlerabstand zum Arbeitsort bei ruhendem und aktivem Panel getrennt prüfen — Separate an active-state sensor offset from a resting-location difference.

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": {
      "fuehler_ruhe_c": "<fuehler_ruhe_c>",
      "platz_ruhe_c": "<platz_ruhe_c>",
      "fuehler_aktiv_c": "<fuehler_aktiv_c>",
      "platz_aktiv_c": "<platz_aktiv_c>",
      "messspielraum_c": "<messspielraum_c>",
      "beide_paare_vergleichbar": "<beide_paare_vergleichbar>"
    },
    "name": "thermostat_punktwaerme_offset_moduswechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
platz_ruhe_cYesZeitgleicher Lufttemperaturwert am Arbeitsort.
platz_aktiv_cYesZeitgleicher Lufttemperaturwert am Arbeitsort im aktiven Zustand.
fuehler_ruhe_cYesSynchroner Thermostatwert im ersten stabilen Ruhezustand.
fuehler_aktiv_cYesThermostatwert im späteren stabilen aktiven Zustand.
messspielraum_cYesBegründeter Spielraum für die Differenz zwischen den beiden Abstandsbeobachtungen.
beide_paare_vergleichbarYesGleiche Messorte und vergleichbare Messgeräte, Luftmessung nach Anleitung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 the behavioral core that the two state measurements are evaluated separately, but it does not say what happens when 'beide_paare_vergleichbar' is false or when the offset exceeds 'messspielraum_c' — error, warning, or silent result is left unknown.

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?

The operation is front-loaded in the first clause, which is good. But the sentence is a bilingual restatement of the same content rather than a progressive elaboration, so roughly half the text is redundant with the other 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?

Six required parameters, no output schema, and a gated comparison — yet the description gives no indication of the result shape or how the tolerance and comparability flag affect the outcome. For a read-only computation tool this is the main missing piece, and the description does not supply it.

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 all six parameters including the comparability gate are already documented in the schema. The description's resting/active framing loosely maps to the four temperature parameters but adds no units, ordering, or tolerance semantics beyond what the schema provides. Baseline 3 applies.

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 German half names a specific operation ('Fühlerabstand zum Arbeitsort ... getrennt prüfen') with a clear resting-vs-active split. However, the English half restates the same idea in vaguer terms ('Separate an active-state sensor offset from a resting-location difference'), and neither sentence says whether the tool returns a verdict, a computed difference, or a stored observation. No differentiation from the many offset/difference siblings is given.

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?

There is no when-to-use / when-not-to-use guidance and no alternative tool is named, despite ~30 siblings including closely related ones (strommessung_gemeinsamer_offset_differenz, punktwaerme_verdeckter_unterschied_koerperzonen). The precondition that both pairs must be comparable is only discoverable from the schema, not the description.

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