Skip to main content
Glama

getecoback-climate-weather

feuchte_versuch_referenzraum

Read-only

Veränderung im Testraum mit einem gleichzeitig beobachteten Referenzraum abgleichen — Compare before-and-after humidity changes against a concurrent reference.

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": {
      "test_vor_rh": "<test_vor_rh>",
      "test_nach_rh": "<test_nach_rh>",
      "referenz_vor_rh": "<referenz_vor_rh>",
      "referenz_nach_rh": "<referenz_nach_rh>",
      "temperatur_vergleichbar": "<temperatur_vergleichbar>"
    },
    "name": "feuchte_versuch_referenzraum"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_vor_rhYesRelative Feuchte im Testraum vor der Maßnahme, in %.
test_nach_rhYesRelative Feuchte im Testraum danach, in %.
referenz_vor_rhYesRelative Feuchte im Referenzraum zum ersten Zeitpunkt, in %.
referenz_nach_rhYesRelative Feuchte im Referenzraum zum zweiten Zeitpunkt, in %.
temperatur_vergleichbarYesWurde geprüft, dass Temperatur und Nutzung beider Reihen vergleichbar blieben?

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 conceptual behavior (differential comparison against a reference, implying the reference series is used to subtract ambient drift), but it says nothing about what the result contains — a raw delta, a corrected delta, or a verdict — and no output schema exists to fill that gap.

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, front-loaded with the operation and the reference-room requirement; nothing superfluous. The German/English duplication costs a little space but serves non-German agents reading the tool.

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?

For a read-only computation over five required inputs with no output schema, the description should at least indicate the shape of the answer (e.g., corrected humidity change). It conveys the comparison concept but leaves the returned quantity and the role of temperatur_vergleichbar's guard-flag semantics implicit.

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 every one of the five parameters is already documented in the schema with units and time-point semantics. The description introduces no additional parameter meaning, which is acceptable at this coverage level but adds no value.

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: reconcile a measured change in the test room against a concurrently observed reference room. The verb 'abgleichen/compare' plus both resources (Testraum, Referenzraum) makes the purpose distinct from raw-reading siblings such as bad_feuchte_erholung_protokoll, though it does not name any sibling explicitly.

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: the phrase 'gleichzeitig beobachteten Referenzraum' hints that a concurrent reference measurement is required for this method, which is a useful selection cue. There is no explicit when-to-use/when-not-to-use statement and no mention of alternatives for cases without a reference room.

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