Skip to main content
Glama

getecoback-climate-weather

entfeuchter_kalt_messvergleich

Read-only

Eigene Kondensatmengen bei zwei Temperaturen vergleichen — Normalize two dehumidifier collection measurements to a day at the same humidity.

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": {
      "cold_l": "<cold_l>",
      "cold_h": "<cold_h>",
      "warmer_l": "<warmer_l>",
      "warmer_h": "<warmer_h>",
      "comparable_humidity_and_settings": "<comparable_humidity_and_settings>"
    },
    "name": "entfeuchter_kalt_messvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
cold_hYesDauer des kälteren Versuchs in Stunden.
cold_lYesGesammeltes Wasser im kälteren Versuch in Litern.
warmer_hYesDauer des wärmeren Versuchs in Stunden.
warmer_lYesGesammeltes Wasser im wärmeren Versuch in Litern.
comparable_humidity_and_settingsYesWaren Luftfeuchte, Gerät, Modus und Messbedingungen 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 the safety profile is covered. The description adds the useful behavioral fact that results are normalized to one day at equal humidity, but it does not disclose what the tool does when comparable_humidity_and_settings is false, nor what form the comparison output takes.

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 sentences with the actionable purpose front-loaded and no filler. The German/English restatement is mildly redundant, but it is a deliberate bilingual gloss rather than bloat.

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?

All five required parameters are fully documented in the schema and the tool is a simple read-only calculation, so the core is covered. However, with no output schema, the description should say what the normalized result looks like (e.g. liters per day per trial and the delta) and how non-comparable inputs are handled.

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 parameter (liters, hours, and the comparability boolean) is already documented in the schema. The description adds only the framing that the two trials are at different temperatures and must share humidity, which the schema already implies; 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 concrete verb and resource: comparing/normalizing one's own condensate amounts from two temperature trials to a per-day figure. It is clear what computation is performed, but it never names a sibling (e.g. entfeuchter_energie_je_liter or entfeuchter_kalt_modellbeleg) to differentiate itself from adjacent dehumidifier calculations.

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 agent can infer it should be called when it has two collection measurements at different temperatures. There is no explicit when-not guidance, no statement about what happens when the comparability flag is false, and no routing to alternative tools.

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