Skip to main content
Glama

getecoback-climate-weather

luftfeuchte_trocknungsprobe_waesche_ortssprung_markieren

Read-only

Trenne die Feuchteänderungen vor und nach dem Umhängen von der offenen Ortswechsel-Lücke — Separate drying observations on either side of a room move

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": {
      "a_vor_rh": "<a_vor_rh>",
      "a_ende_rh": "<a_ende_rh>",
      "b_start_rh": "<b_start_rh>",
      "b_spaet_rh": "<b_spaet_rh>",
      "je_paar_vergleichbar": "<je_paar_vergleichbar>"
    },
    "name": "luftfeuchte_trocknungsprobe_waesche_ortssprung_markieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_vor_rhYesFrüherer Zimmerwert vor dem Umhängen
a_ende_rhYesLetzter Wert desselben Punktes vor dem Umhängen
b_spaet_rhYesSpätere Ablesung desselben Punktes im neuen Raum
b_start_rhYesErster Wert am markierten Punkt des neuen Raums
je_paar_vergleichbarYesJe Raum bekannte und ausreichend ähnliche Temperaturen und Messpunkte

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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. Beyond that the description adds only a conceptual framing: it says nothing about what is returned (a delta, a verdict, a residual), whether the result depends on the boolean gate, or in what units the comparison is expressed.

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?

Two short sentences, front-loaded, with no filler — but the German and English lines are near-duplicates rather than complementary, so the second sentence earns little space. The metaphorical wording also costs clarity that a shorter plain statement would have bought.

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?

Five required numeric parameters, no output schema, and a comparison-style computation: the description should at minimum explain what the caller receives and why the comparability flag gates the result. Neither is present, leaving the agent unable to predict the outcome of a call.

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 the baseline is 3. The description's "vor und nach dem Umhängen" loosely maps onto the a_* (before) and b_* (after) parameter pairs, and the "Lücke" hints at the je_paar_vergleichbar gate, but it supplies no additional syntax, ranges, or interpretation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does convey a concept — separating humidity changes on either side of a room move — but it is phrased abstractly ("offene Ortswechsel-Lücke") and never states plainly that the tool compares paired readings before and after relocation. It gives no differentiation from near-neighbours such as waesche_trocknung_teilserie_raumwechsel or arbeitsplatz_raumwechsel_persoenliche_hitzepause, so an agent must guess which humidity-comparison tool applies.

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 when-to-use statement, no prerequisite (e.g. that both rooms need comparable temperatures/measurement points), and no alternative named. The only conditionality lives in the schema's je_paar_vergleichbar parameter, not in the description.

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