Skip to main content
Glama

getecoback-climate-weather

luftkuehler_nass_trocken_einlassabgleich

Read-only

Vergleicht die lokale Abkühlung am Auslass mit dem jeweiligen Einlasswert zweier erprobter Betriebsarten — Compare wet and dry outlet cooling against each run’s own intake temperature.

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": {
      "nass_ein_c": "<nass_ein_c>",
      "nass_aus_c": "<nass_aus_c>",
      "trocken_ein_c": "<trocken_ein_c>",
      "trocken_aus_c": "<trocken_aus_c>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "luftkuehler_nass_trocken_einlassabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
nass_aus_cYesTrockener Sensor im Auslass-Luftstrom in °C.
nass_ein_cYesTrockener Sensor am Einlass in der Nassprobe in °C.
vergleichbarYesGleicher Luftstrom, gleiche Geometrie, vergleichbare Feuchte und Betriebsdauer? Beide Betriebsarten sind dokumentiert.
trocken_aus_cYesAuslasswert in dieser Probe in °C.
trocken_ein_cYesEinlasswert in der dokumentierten trockenen Probe in °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare a read-only, closed-world operation, so safety needs no restating. The description does add one real behavioral constraint – each outlet value is compared against its own run's intake rather than cross-comparing wet and dry – but it says nothing about what the comparison produces or how the result 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the core comparison is stated before the qualifier. The German/English duplication costs some length but aids cross-language agents, so it is defensible rather than wasteful.

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?

With no output schema, the description carries the burden of saying what comes back – a delta in Kelvin, a per-mode verdict, or a comparability judgement – and it does not. The inputs and the analytical intent are adequately covered, but the result side is a genuine gap for a computation tool taking five required numbers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns an extra point by resolving the parameter pairing that the schema wording muddles (e.g. 'nass_aus_c' described as a 'trockener Sensor'): it makes clear that nass_aus pairs with nass_ein and trocken_aus with trocken_ein. It does not, however, explain the consequence of the 'vergleichbar' boolean.

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 gives a specific verb ('Vergleicht') and a specific object: outlet cooling in each of two tested operating modes measured against that mode's own intake temperature. An agent gets the analytical intent, but the definition never names which sibling (e.g. a single-mode outlet measurement or a run-comparison tool) it replaces, so differentiation is left to the identifier.

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 'zweier erprobter Betriebsarten' plus the required 'vergleichbar' flag signal that this is for a paired wet-vs-dry run that is already documented and comparable. There is no explicit statement of when to choose this over the many outlet-measurement or comparison siblings, and no when-not condition.

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