Skip to main content
Glama

getecoback-climate-weather

raum_temperaturschichtung_messen

Read-only

Temperaturunterschied zwischen Bodennähe und Kopfhöhe aus Vergleichsmessungen erkennen — Check for a vertical air temperature gradient at one indoor location.

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": {
      "unten_c": "<unten_c>",
      "oben_c": "<oben_c>",
      "hoehenabstand_m": "<hoehenabstand_m>",
      "fehler_je_c": "<fehler_je_c>"
    },
    "name": "raum_temperaturschichtung_messen"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_cYesGleichzeitig gemessene obere Lufttemperatur in °C.
unten_cYesGleichzeitig gemessene Lufttemperatur unten in °C.
fehler_je_cYesAbsoluter Messfehler pro Thermometer in °C.
hoehenabstand_mYesSenkrechter Abstand beider Messpunkte in Metern.

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 safe, closed-world character is covered. The description adds the notion that inputs are comparison measurements at one location, which is behavioral context beyond the annotations. It does not say what the evaluation produces or how a 'detected' gradient is characterized, leaving a gap for a pure-computation tool.

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 clauses, German then English, with the action and the constraint front-loaded and no filler. The bilingual duplication is mildly redundant but keeps the definition under two lines, so it costs little.

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?

The tool is a four-required-parameter computation with no output schema, so the description should ideally state what comes back (a gradient in K/m, a pass/fail, a per-metre value). It does not, and the role of fehler_je_c in the result is left unexplained. Parameter coverage is excellent, but the output-side gap is real for a calculator.

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%: all four parameters carry bounds and German explanations, including the requirement that both temperatures be measured simultaneously. The description adds no syntax, unit, or interpretation guidance beyond that, so the baseline of 3 is appropriate.

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 concrete verb and object: 'Check for a vertical air temperature gradient at one indoor location', refined by 'Temperaturunterschied zwischen Bodennähe und Kopfhöhe'. That is specific enough for an agent to know this is a comparison-measurement evaluation tool rather than a sensor reader or a heating-load calculator. It stops short of naming a sibling to differentiate from, so it lands at 4 rather than 5.

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: 'at one indoor location' and 'aus Vergleichsmessungen' suggest the tool applies when you already have two simultaneous readings at the same spot. There is no explicit when-to-use, when-not-to-use, or alternative tool named among the many measurement siblings (e.g. dusche_temperatur_streuung, klima_zu_und_rueckluft_messen). The agent must infer the boundary itself.

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