Skip to main content
Glama

getecoback-raumklima

lueftungsversuch_wetterpaare_eignung

Read-only

Zwei Lüftungsläufe anhand beobachteter Außenwerte vor dem A/B-Vergleich zusammenstellen — Screen ventilation pairs against declared outdoor temperature and humidity tolerances.

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": {
      "a_aussen_c": "<a_aussen_c>",
      "b_aussen_c": "<b_aussen_c>",
      "a_aussen_rh": "<a_aussen_rh>",
      "b_aussen_rh": "<b_aussen_rh>",
      "thermischer_spielraum_c": "<thermischer_spielraum_c>",
      "feuchtespielraum_pp": "<feuchtespielraum_pp>"
    },
    "name": "lueftungsversuch_wetterpaare_eignung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_aussen_cYesAußentemperatur vor Lauf A, in °C.
b_aussen_cYesAußentemperatur vor Lauf B, in °C.
a_aussen_rhYesRelative Außenfeuchte vor Lauf A, in %.
b_aussen_rhYesRelative Außenfeuchte vor Lauf B, in %.
feuchtespielraum_ppYesVorher gewählter Spielraum der relativen Außenfeuchte, in Prozentpunkten.
thermischer_spielraum_cYesVorher gewählter Spielraum beim Temperaturunterschied, in °C.

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 agent knows this is a safe, self-contained computation. The description adds that the screening is against 'declared' tolerances supplied as inputs, which is genuinely useful context beyond the annotations. It does not disclose the output shape (a verdict? a distance measure?) or whether supplied tolerances interact, leaving a real gap for a decision tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The guidance is front-loaded, but the content is stated twice, once in German and once in English, without either version adding information the other lacks. The bilingual duplication is defensible for language robustness yet still wastes half the description on a restatement.

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?

Six required numeric parameters with no output schema and no mention of what the caller receives make the return semantics the main missing piece. For a screening/eligibility tool, the agent needs to know whether it gets a boolean, a reason, or a margin value. Otherwise the description is adequate for the inputs it accepts.

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 description coverage is 100%, so the six parameters are already documented individually, and the baseline would be 3. The description does add modest framing by grouping them conceptually into 'outdoor temperature and humidity' values versus 'declared tolerances', clarifying that the Spielraum parameters are user-chosen thresholds rather than measured values. That is a small but real semantic gain over the schema.

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 concrete action and object: take two ventilation runs' observed outdoor values and screen them against declared tolerances before an A/B comparison. The English half of the sentence ('Screen ventilation pairs against declared outdoor temperature and humidity tolerances') makes the pass/fail screening intent explicit. It does not distinguish this from any sibling tool, so it stops short of a 5.

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 'vor dem A/B-Vergleich' positions the tool in a workflow and implies when to call it (before a paired comparison). However, it never states when not to use it, what the alternative is if the pair is rejected, or any prerequisite such as the tolerances having been chosen beforehand. Usage is implied rather than prescribed.

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