Skip to main content
Glama

getecoback-raumklima

hygrometer_zweipunkt_referenz_abgleich

Read-only

Feuchteanzeige zwischen zwei extern belegten Referenzpunkten linear einordnen — Estimate a bounded two-point humidity comparison without extrapolating.

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": {
      "anzeige_tief_rh": "<anzeige_tief_rh>",
      "anzeige_hoch_rh": "<anzeige_hoch_rh>",
      "referenz_tief_rh": "<referenz_tief_rh>",
      "referenz_hoch_rh": "<referenz_hoch_rh>",
      "anzeige_neu_rh": "<anzeige_neu_rh>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "hygrometer_zweipunkt_referenz_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
vergleichbarYesReferenzwerte unabhängig belegt und Bedingungen einschließlich Temperatur vergleichbar?
anzeige_neu_rhYesAnzeige, für die der Vergleichswert eingeordnet werden soll.
anzeige_hoch_rhYesVerglichene Anzeige am höheren Prüfpunkt.
anzeige_tief_rhYesVerglichene Anzeige am niedrigeren Prüfpunkt.
referenz_hoch_rhYesExterner Referenzwert am höheren Prüfpunkt.
referenz_tief_rhYesExterner Referenzwert am niedrigeren Prüfpunkt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 genuine behavioral context — interpolation is linear and never extrapolates beyond the reference interval — but stays silent on what happens when 'vergleichbar' is false and on the shape of the computed result.

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 compact sentence with the core constraint front-loaded; the bilingual restatement is slightly redundant but adds no confusion and no wasted preamble.

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?

For a six-parameter, all-required computation tool with no output schema, the definition covers the input story but not the output story (what value is produced, in what unit/format) nor the semantics of the 'vergleichbar' gate. Adequate but leaves real gaps an agent may hit at call time.

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 are already documented in the schema. The description contributes the framing that the two reference points must be externally documented and that the interpolation is linear, but adds no per-parameter detail beyond that framing; baseline 3 applies.

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?

The description names a specific operation and resource: linearly positioning a humidity reading between two externally documented reference points, and explicitly bounding it ('without extrapolating'). This separates it from measurement/reading siblings in the hygrometer family, though it never names an alternative tool.

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 an implicit applicability constraint ('bounded', 'without extrapolating'), but no explicit statement of when to use this versus related hygrometer tools, and no guidance on what to do when the required 'vergleichbar' flag is false.

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