Skip to main content
Glama

getecoback-climate-weather

kwl_sommerbypass_kuehlgewinn_probe

Read-only

Bei aktiver Nachtlüftung die gemessene Zuluft mit offenem und geschlossenem Sommer-Bypass vergleichen — Compare matched summer bypass supply temperatures against a personal target.

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": {
      "zu_offen_c": "<zu_offen_c>",
      "zu_geschlossen_c": "<zu_geschlossen_c>",
      "zuluft_ziel_c": "<zuluft_ziel_c>",
      "gleiche_bedingungen": "<gleiche_bedingungen>"
    },
    "name": "kwl_sommerbypass_kuehlgewinn_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
zu_offen_cYesZulufttemperatur bei offen bestätigtem Bypass. In °C.
zuluft_ziel_cYesEigene gewünschte maximale Zulufttemperatur für den Vergleich. In °C.
zu_geschlossen_cYesZulufttemperatur bei geschlossen bestätigtem Bypass. In °C.
gleiche_bedingungenYesGleiche Außentemperatur, Ablufttemperatur und Lüfterstufe, keine Zusatzkühlung?

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 safety profile is covered. The description adds the important behavioral qualifier 'matched' (comparison only valid under identical conditions), but it says nothing about what the tool returns or how it treats unmatched inputs beyond the schema's boolean.

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 puts the night-ventilation condition first and the action second, with no filler. The German/English duplication is slightly redundant but functions as a gloss rather than padding.

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?

For a four-parameter read-only comparison with full schema coverage and no output schema, the definition covers inputs adequately. The gap is that no output schema exists and the description never hints at what the comparison produces (verdict, delta, recommendation), leaving the agent to guess the return shape.

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 all four parameters are already documented, including the bounds and the conditions boolean. The description reinforces that both temperatures are measured and that one is a personal target, but adds no format or semantics beyond the schema; baseline 3 applies.

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 verb (compare) and a precise resource (measured supply-air temperature with summer bypass open vs closed), plus the comparison against a personal target. It is clear enough to distinguish from the seasonally different sibling kwl_winter_rueckwaerme_messquote, but it does not explicitly differentiate itself from any sibling.

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?

'Bei aktiver Nachtlüftung' states a precondition, so the agent knows this is a night-ventilation scenario. However, there is no statement of when not to use it and no named alternative, so the routing guidance is only implied.

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