Skip to main content
Glama

getecoback-raumklima

luftkuehler_feuchteband_paarprobe_auslassnutzen

Read-only

Vergleicht gemessenen lokalen Zusatznutzen einer Nassstufe aus zwei getrennt beobachteten Feuchtebereichen — Compare measured wet-mode benefit in two evidenced humidity bands.

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": {
      "start_a": "<start_a>",
      "start_b": "<start_b>",
      "nutzen_a_c": "<nutzen_a_c>",
      "nutzen_b_c": "<nutzen_b_c>",
      "ausser_feuchte_gleich": "<ausser_feuchte_gleich>"
    },
    "name": "luftkuehler_feuchteband_paarprobe_auslassnutzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_aYesStart der vergleichbaren Probenreihe A in % relativer Feuchte.
start_bYesStart der Probenreihe B am selben Einlass in % relativer Feuchte.
nutzen_a_cYesAus gepaarten Nass- und Trockenproben gemessener lokaler Zusatzabfall A in °C.
nutzen_b_cYesEntsprechend gemessener lokaler Zusatzabfall B in °C.
ausser_feuchte_gleichYesTemperatur, Luftführung und Auswertung sind vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is covered, but the description adds nothing about the outcome of the comparison or what the agent receives. With no output schema, the description should at least indicate whether a computed benefit delta is returned and what happens when ausser_feuchte_gleich is false (rejection vs. warning) — neither is disclosed.

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 bilingual sentence with the verb front-loaded and no filler. The duplicated German/English phrasing is slightly wasteful but aids disambiguation of the opaque tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A five-required-parameter analytical tool with no output schema needs the description to explain what result is produced and how the comparability flag gates the computation. Neither is present, so an agent knows the inputs but not the outcome or failure mode.

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%, with each parameter documented in German including units (% relative humidity, °C) and bounds. The description repeats the two-band concept but adds no syntax, range, or interpretation detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ("Vergleicht") and resource ("gemessenen lokalen Zusatznutzen einer Nassstufe") scoped to two separately observed humidity bands, so the operation is identifiable. However, the dense bilingual compound wording and the absence of any contrast with closely related siblings (e.g. the Nass-Trocken inlet comparison or per-degree moisture tools) leave the agent guessing whether this is the right comparison instrument.

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 when-to-use guidance, no prerequisite statement, and no pointer to an alternative tool. The agent must infer from the title-like name when this paired-sample comparison applies rather than, say, a simple wet/dry inlet balance.

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