Skip to main content
Glama

getecoback-climate-weather

heizwaesche_relative_und_absolute_richtung

Read-only

Sinkende relative Feuchte bei zunehmender absoluter Feuchte als unterschiedliche Beobachtung einordnen — Interpret opposing humidity changes during a drying trial.

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": {
      "gleicher_messort": "<gleicher_messort>",
      "rh_vor": "<rh_vor>",
      "rh_nach": "<rh_nach>",
      "abs_vor": "<abs_vor>",
      "abs_nach": "<abs_nach>",
      "rh_spanne": "<rh_spanne>",
      "abs_spanne": "<abs_spanne>"
    },
    "name": "heizwaesche_relative_und_absolute_richtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
rh_vorYesRelative Feuchte vor der Phase in %.
abs_vorYesAus Messwerten ermittelte absolute Feuchte vorher in g/m³.
rh_nachYesRelative Feuchte nach der Phase in %.
abs_nachYesAbsolute Feuchte nachher in g/m³.
rh_spanneYesGemeinsame Unsicherheit in Prozentpunkten.
abs_spanneYesGemeinsame Unsicherheit der absoluten Werte in g/m³.
gleicher_messortYesSind Zeitachse, Messort und Berechnungsgrundlage an beiden Punkten vergleichbar?

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 safety is covered. The description adds the interpretive framing (treating opposing humidity trends as distinct observations), but says nothing about what the classification result looks like or how it handles the comparability flag and uncertainty spans, which is the substantive behavior here.

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 compact sentence, bilingual, with the operative condition front-loaded. Nothing is wasted, though the German and English halves are largely duplicative and the English gloss drops some nuance.

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 seven required parameters and no output schema, the description should at least indicate what kind of result the classification yields; it does not. The input side is fully covered by the schema, so an agent could call it, but the meaning of the returned judgment must be guessed.

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 seven parameters (including the gleicher_messort comparability flag and both uncertainty spans) are already documented in the schema. The description adds no additional meaning about units, tolerances, or how the spans affect the interpretation, 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?

The description names a specific interpretive operation ('einordnen' / 'Interpret') applied to a specific condition: falling relative humidity combined with rising absolute humidity during a drying trial. That is far more concrete than a restatement of the tool name, though it does not explicitly distinguish this scenario from the many similarly narrow heizwaesche_* siblings.

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 by the phrase 'during a drying trial' and the opposing-direction condition; there is no explicit statement of when to choose this tool over the other heizwaesche classification tools, nor any exclusion or prerequisite guidance such as what to do when the measurement sites 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