Skip to main content
Glama

getecoback-raumklima

punktwaerme_zwei_hoehen_reihenfolgewechsel

Read-only

Ermitteln, ob die bevorzugte Höhe am Arbeitspunkt zwischen zwei tatsächlich geprüften Aufstellungen wechselte — Detect a measured reversal of the vertical temperature ordering.

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": {
      "a_tief_c": "<a_tief_c>",
      "a_hoch_c": "<a_hoch_c>",
      "b_tief_c": "<b_tief_c>",
      "b_hoch_c": "<b_hoch_c>",
      "gesamtspielraum_c": "<gesamtspielraum_c>",
      "fenster_passend": "<fenster_passend>"
    },
    "name": "punktwaerme_zwei_hoehen_reihenfolgewechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_hoch_cYesZeitgleiche Messung an der oberen Nutzposition in A.
a_tief_cYesMessung an der unteren Nutzposition in der bereits geprüften Aufstellung A.
b_hoch_cYesZeitgleiche Messung am selben oberen Punkt in B.
b_tief_cYesMessung an exakt derselben unteren Position in der geprüften Aufstellung B.
fenster_passendYesStimmen Messaufbau, Fensterdauer und übrige Bedingungen hinreichend überein?
gesamtspielraum_cYesSpielraum je Höhendifferenz, unterhalb dessen ihre Richtung offen bleibt.

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 that the comparison is only valid between setups that were genuinely measured, but it never states the return form (a boolean reversal flag, a classification, or a three-way verdict given that the schema's Gesamtspielraum lets direction "remain open"). That gap matters for an agent that must interpret the 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 bilingual sentence with the operative German clause front-loaded and a terse English gloss. The bilingual duplication costs a little space but aids disambiguation and nothing is padded.

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?

Six required numeric/boolean inputs with no output schema mean the description carries the burden of explaining what comes back, and it only implies a yes/no verdict. The threshold concept (Spielraum below which the direction stays undetermined) lives solely in the schema, leaving the result interpretation underspecified for a pure computation tool.

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 the six parameters (a_tief_c, a_hoch_c, b_tief_c, b_hoch_c, gesamtspielraum_c, fenster_passend) are already fully documented with ranges and semantics. The description contributes only the framing that the two setups are paired measurements; it adds no per-parameter meaning beyond the schema, so the 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?

"Ermitteln, ob die bevorzugte Höhe am Arbeitspunkt zwischen zwei tatsächlich geprüften Aufstellungen wechselte" names a specific verb (determine) and a specific computed quantity (a reversal of vertical temperature ordering across two measured setups), reinforced by an English gloss. An agent knows exactly what verdict this tool produces, though nothing in the text distinguishes it from neighbouring punktwaerme_* diagnostic tools.

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?

The only guidance is embedded in the noun phrase "tatsächlich geprüften Aufstellungen", which hints that both arrangements must already be measured. There is no statement of when to prefer this over sibling diagnostics (e.g. raumdurchschnitt_verdeckt_festen_platz or verdeckter_unterschied_koerperzonen), no exclusions, and no mention of what to do when the data are not comparable.

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