Skip to main content
Glama

getecoback-climate-weather

luftkuehler_mehrfeuchte_je_lokalgrad_probe

Read-only

Bezieht einen gemessenen Feuchtezuwachs im Raum auf den beobachteten Kühlgewinn im örtlichen Luftstrom — Relate a measured room humidity change to an observed local cooling benefit.

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": {
      "mehrfeuchte_g_m3": "<mehrfeuchte_g_m3>",
      "lokaler_gewinn_c": "<lokaler_gewinn_c>",
      "temp_messspiel": "<temp_messspiel>",
      "laeufe_paarig": "<laeufe_paarig>"
    },
    "name": "luftkuehler_mehrfeuchte_je_lokalgrad_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
laeufe_paarigYesZeitgleich abgeglichene lokale Luftwerte und getrennte Raumwerte in passenden Nass-Trocken-Proben?
temp_messspielYesEigene Unterscheidungsbreite der Temperaturmessung in °C.
lokaler_gewinn_cYesZusätzlicher gemessener Temperaturabfall am Nutzplatz in °C.
mehrfeuchte_g_m3YesDifferenz der absoluten Raumfeuchte zur vergleichbaren Trockenprobe in g/m³.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 profile is covered and the description's job is lighter. It does add that the operation relates two measurements rather than performing a physical action, but it never says what the result looks like (a ratio, a normalized value) despite there being 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?

A single compact sentence with the key relationship front-loaded and no wasted clauses. The German/English duplication is redundant in length but does not obscure the meaning and may be intentional for a bilingual catalog.

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 four required parameters are fully described and the annotations cover read-only behavior, so basic callability is complete. However, for a computed derived metric with no output schema, the description should state the nature of the returned value, and it does not.

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 including units, ranges and the laeufe_paarig pairing flag is already documented in the schema. The description restates the conceptual pairing of humidity and local cooling but adds no syntax, unit or preprocessing guidance beyond it, which is the expected baseline.

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: relating a measured room humidity increase to an observed local cooling gain in the airflow. That is a distinct derived-ratio computation, not a generic measurement, so an agent can tell what the tool produces. It stops short of naming the closely related sibling probes (e.g. luftkuehler_feuchteband_paarprobe_auslassnutzen) that could otherwise be confused with it.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The conditions that select this tool over other luftkuehler probe tools must be inferred from the description's phrasing alone.

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