Skip to main content
Glama

getecoback-raumklima

hygrometer_standorttausch_auswerten

Read-only

Zwei Hygrometer an zwei festen Messorten tauschen und Standort- von Sensorunterschieden trennen — Separate position effects from sensor offsets using a crossover.

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_ort_1_rh": "<a_ort_1_rh>",
      "b_ort_2_rh": "<b_ort_2_rh>",
      "a_ort_2_rh": "<a_ort_2_rh>",
      "b_ort_1_rh": "<b_ort_1_rh>",
      "standorte_stabil": "<standorte_stabil>"
    },
    "name": "hygrometer_standorttausch_auswerten"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_ort_1_rhYesMessphase 1: Hygrometer A am Ort 1, in %.
a_ort_2_rhYesMessphase 2: Hygrometer A am Ort 2 nach Eingewöhnung, in %.
b_ort_1_rhYesMessphase 2: Hygrometer B am Ort 1 nach Eingewöhnung, in %.
b_ort_2_rhYesMessphase 1: Hygrometer B am Ort 2, in %.
standorte_stabilYesWaren beide Orte zwischen den Messphasen vergleichbar, einschließlich Temperatur, Nutzung und Zugluft?

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 and the description correctly adds that this is a pure evaluation separating position from sensor offset. It does not disclose what the result contains (per-sensor offset vs. per-location difference), which matters given there is no output schema.

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 tight sentences with the operation and the analytical goal front-loaded; nothing is padded. The German/English duplication costs a little space but reinforces precision rather than adding noise.

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 five-required-parameter computation with no output schema, the description explains the input design well but leaves the returned quantities entirely unstated. An agent knows what to feed in but not what it will get back, which is the main remaining gap.

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 coverage is 100% and each of the four RH values is labeled with phase and device/location, so the schema carries parameter meaning on its own. The description adds no interpretation of the inputs beyond the crossover concept — baseline 3 is appropriate.

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 concrete verb pair ('tauschen' / 'trennen' — swap and separate) and the resource (two hygrometers at two fixed locations), and 'crossover' pins down the method. It is clear what the tool computes, though it does not name the sibling analyses it differs from.

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 crossover framing: the agent can infer the tool applies after a completed swap with acclimation. There is no explicit statement of when to use this versus e.g. hygrometer_messort_pruefen or hygrometer_grenzuebertritt_zeitfenster, and no stated preconditions.

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