Skip to main content
Glama

getecoback-raumklima

fenster_taureserve_wechsel_frueher_als_beschlag

Read-only

Prüfe, ob die gemessene Taupunktreserve schon vor sichtbarem Beschlag kleiner wurde — Compare dew-point margin before the first observed condensation

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": {
      "glas_a_c": "<glas_a_c>",
      "tau_a_c": "<tau_a_c>",
      "glas_b_c": "<glas_b_c>",
      "tau_b_c": "<tau_b_c>",
      "spaeter_beschlag_belegt": "<spaeter_beschlag_belegt>",
      "messorte_gepaart": "<messorte_gepaart>"
    },
    "name": "fenster_taureserve_wechsel_frueher_als_beschlag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tau_a_cYesTaupunkt der zugehörigen Raumluft zur ersten Messung
tau_b_cYesTaupunkt der zugehörigen Raumluft zur zweiten Messung
glas_a_cYesFrüherer innerer Scheibenwert am betrachteten Punkt
glas_b_cYesSpäterer Scheibenwert am selben Punkt, noch ohne sichtbaren Beschlag
messorte_gepaartYesWerte aus jeweils zeitlich passenden Messpaaren
spaeter_beschlag_belegtYesSichtbarer Beschlag wurde erst nach diesen Ablesungen an demselben Punkt festgehalten

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description is not contradicted. The description adds the framing that this is a pure verification/comparison, but it does not disclose what the check produces — no verdict, threshold, or tolerance is mentioned, and there is no output schema to fall back on.

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 with the core condition front-loaded and nothing extraneous; the German/English duplication is a minor length cost that aids comprehension rather than wasting space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six required parameters, no output schema, and no explanation of the computed result, the description leaves an agent guessing what comes back (a boolean? a margin delta?). For an analytical tool whose entire value is its verdict, that gap is significant relative to the modest annotation coverage.

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 (the two glass readings, two dew points, paired-site flag, and later-condensation flag) are already documented in the schema. The description adds no extra semantics such as expected units, measurement pairing rules, or how the margin is computed, so the baseline of 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 check ('Prüfe, ob die gemessene Taupunktreserve schon vor sichtbarem Beschlag kleiner wurde') with a precise condition and resource, so an agent understands this is a comparison of dew-point margin against a later condensation observation. It does not, however, distinguish itself from nearby siblings such as fenster_beschlag_einordnen or fenster_oberflaeche_taucheck.

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 statement of when to use this versus an alternative, no prerequisite conditions, and no exclusions. The only usage signal is implicit in the required paired-measurement parameters, which the agent must infer.

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