Skip to main content
Glama

getecoback-raumklima

hygrometer_grenzuebertritt_zeitfenster

Read-only

Ungefähres Zeitfenster einer beobachteten Feuchteüberschreitung zwischen zwei Ablesungen benennen — Report the observation bracket for a threshold crossing between sparse samples.

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": {
      "vorher_min": "<vorher_min>",
      "nachher_min": "<nachher_min>",
      "vorher_rh": "<vorher_rh>",
      "nachher_rh": "<nachher_rh>",
      "pruefwert_rh": "<pruefwert_rh>"
    },
    "name": "hygrometer_grenzuebertritt_zeitfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_rhYesRelative Luftfeuchte bei der ersten Ablesung, in %.
nachher_rhYesRelative Luftfeuchte bei der zweiten Ablesung, in %.
vorher_minYesZeitpunkt der ersten Ablesung in Minuten ab gemeinsamem Nullpunkt.
nachher_minYesZeitpunkt der zweiten Ablesung in Minuten ab demselben Nullpunkt.
pruefwert_rhYesSelbst gewähltes Beobachtungssignal, in %.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description still adds real behavioral context beyond them: the result is explicitly approximate ('Ungefähres' / 'observation bracket'), meaning the tool interpolates between two sparse samples and returns a range, not a precise crossing moment. It stops short of describing output shape or how the bracket is derived.

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 tightly written clauses with the core idea front-loaded. The German and English halves are near-duplicates, which costs some space, but the bilingual phrasing aids matching on either term and no sentence is filler.

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?

With five required numeric parameters and no output schema, the description should say what comes back (a start/end pair in minutes? a single estimated instant?) and how the bracket is derived from pruefwert_rh versus vorher_rh/nachher_rh. It conveys the approximation concept but leaves the return shape and edge-case behavior (no crossing occurs, both readings on the same side) unspecified.

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%, with each of the five parameters documented in-schema (units, ranges, shared zero point). The description only restates that two readings are involved ('zwischen zwei Ablesungen'), adding no semantics beyond what the schema already provides; baseline 3 applies. It notably does not explain how 'pruefwert_rh' acts as the observation signal relative to the other values.

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 on a specific resource: naming ('benennen') an approximate time window ('Zeitfenster') for an observed humidity threshold crossing between two readings. The verb+resource pairing is unambiguous, and the English half confirms the German. It does not, however, distinguish itself from the many sibling '*_zeitfenster' tools (e.g. fassadenbeschattung_zeitfenster_ueberlappung, messprotokolle_zeitfenster_schneiden).

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 explicit when-to-use, when-not-to-use, or alternative routing. The phrase 'between sparse samples' hints at the situation (widely spaced readings, so the crossing time is only bounded), but the agent must infer that this is the right tool whenever a threshold crossing must be bracketed rather than computed exactly. No sibling is named as an alternative or exclusion.

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