Skip to main content
Glama

getecoback-climate-weather

luftkuehler_auslassmessung_nasser_fuehler_ausschluss

Read-only

Prüft ob ein aufgezeichneter Auslasswert zur trockenen Lufttemperatur-Messung taugt — Flag an outlet measurement exposed to wetting of the temperature sensor.

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": {
      "auslass_c": "<auslass_c>",
      "fuehler": "<fuehler>",
      "messweg_frei": "<messweg_frei>"
    },
    "name": "luftkuehler_auslassmessung_nasser_fuehler_ausschluss"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuehlerYesDokumentierter Zustand des Temperaturfühlers.
auslass_cYesVorliegender Wert am Auslass in °C.
messweg_freiYesWar der Fühler frei im Austrittsstrom und ohne Kontakt zur Matte oder zum Gehäuse?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the substantive criterion — sensor wetting disqualifies the reading — but says nothing about the outcome (what a flag/verdict looks like, or how 'nicht_beobachtet' is treated), which matters since 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?

A single front-loaded sentence with the verb and criterion first, followed by a short English gloss. The bilingual duplication is mild redundancy but the content is dense and waste-free.

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 three required parameters are fully documented in the schema and annotations cover the safety profile, so input-side completeness is fine. The gap is output-side: for a pass/fail suitability check with no output schema, the description should say what verdict is returned and how ambiguous sensor states are resolved.

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 genuinely adds the decision logic that ties the parameters together: wetting of the sensor and suitability for dry temperature measurement explain why 'fuehler' and 'messweg_frei' gate the result, beyond their individual schema descriptions.

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?

States a specific verb and object: it checks whether a recorded outlet value is usable for dry air temperature measurement, and the English half adds the concrete failure mode (wetting of the sensor). An agent can tell this is a validity/flag check rather than a measurement or configuration tool, though it never names a sibling to contrast with.

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?

The phrase 'aufgezeichneter Auslasswert' implies the input precondition (a recorded outlet reading exists) and the dry-measurement context implies when the check matters, but there is no explicit when-to-use/when-not statement and no alternative tool is named despite many related siblings.

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