Skip to main content
Glama

getecoback-climate-weather

raumluft_zielwert_erreichung_nach_start

Read-only

Wertet aus, zwischen welchen Messzeitpunkten ein eigener Temperaturzielwert erstmals beobachtet wurde — Locate the first sampled time window meeting a user-chosen room temperature target.

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": {
      "ziel_c": "<ziel_c>",
      "start_c": "<start_c>",
      "erster_wert_c": "<erster_wert_c>",
      "zweiter_wert_c": "<zweiter_wert_c>",
      "erster_min": "<erster_min>",
      "zweiter_min": "<zweiter_min>"
    },
    "name": "raumluft_zielwert_erreichung_nach_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_cYesEigener Vergleichszielwert in °C.
start_cYesMesswert bei Beginn in °C.
erster_minYesZeitpunkt des ersten Messpunkts seit Beginn in Minuten.
zweiter_minYesZeitpunkt des zweiten Messpunkts seit Beginn in Minuten.
erster_wert_cYesTemperatur zum ersten Messpunkt nach Beginn in °C.
zweiter_wert_cYesTemperatur zum zweiten Messpunkt in °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this a safe, closed-world read/compute operation, so the safety profile is covered. The description, however, leaves the actual computation opaque: it never says whether the crossing point is found by linear interpolation between erster_wert_c and zweiter_wert_c, what happens when the target is never reached, or what the result looks like. For a pure-calculation tool the algorithm is the key behaviour worth disclosing.

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 definition is short and front-loads the core statement, but it says the same thing twice in German and English, which is redundant rather than reinforcing. No wasted length beyond that duplication.

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?

All six required parameters are fully described in the schema and there is no output schema, so the description should explain what is returned — a time window or a pair of minutes — yet only hints at it via "zwischen welchen Messzeitpunkten". For a six-parameter calculation tool with no output schema, the return value and no-hit behaviour are missing.

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 with units and ranges. The description only reinforces that ziel_c is a self-chosen target and that the tool works across measurement time points; it adds no interpolation logic or constraint relationships beyond the schema. 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?

States a specific analysis verb ("Wertet aus") plus the exact quantity computed: the time window between samples where a user-supplied temperature target is first met. The English gloss confirms the same scope, so an agent understands the operation without opening the schema. It does not, however, differentiate itself from the many other raumluft_* siblings.

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 statement of when to pick this tool over neighbouring room-air analysis tools, no prerequisites, and no exclusions. The only implied guidance is that a target temperature must be user-chosen, which is already evident from the ziel_c parameter.

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