Skip to main content
Glama

getecoback-climate-weather

klima_heizbetrieb_winterdaten_abgleich

Read-only

Herstellerwerte für Heizbetrieb am kalten Auslegungspunkt einordnen — Check heating data coverage for the planned outdoor conditions.

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": {
      "ziel_aussen_c": "<ziel_aussen_c>",
      "geprueft_aussen_c": "<geprueft_aussen_c>",
      "min_betrieb_c": "<min_betrieb_c>",
      "ausfuehrung_geprueft": "<ausfuehrung_geprueft>"
    },
    "name": "klima_heizbetrieb_winterdaten_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
min_betrieb_cYesBestätigte untere Betriebsgrenze fürs Heizen laut Anleitung.
ziel_aussen_cYesEigene relevante Außentemperatur in Grad Celsius.
geprueft_aussen_cYesAußentemperatur des veröffentlichten Heizprüfpunkts.
ausfuehrung_geprueftYesBetreffen Heizgrenze und Prüfdaten das exakte Modell?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety and locality are covered. The description adds that this is an interpretive 'Einordnen' of manufacturer values at the cold design point, which suggests a comparison/verdict rather than a data fetch, but it says nothing about what the verdict or output looks like, and no output schema exists to fill that gap.

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?

The purpose is front-loaded in a single short sentence with no padding. The German and English halves are near-duplicates rather than complementary, which is a small inefficiency but not harmful.

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 read-only four-parameter assessment tool with no output schema, the definition covers the input intent adequately but leaves the agent guessing what a successful result contains and how the 'coverage' judgement is expressed. A brief note on the returned classification would complete it.

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 coverage is 100%, so all four parameters are already documented in the schema. The description adds no extra meaning about how ziel_aussen_c, geprueft_aussen_c, min_betrieb_c and ausfuehrung_geprueft interact (e.g. that the comparison is only valid when ausfuehrung_geprueft is true), so the 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 concrete activity (checking/einordnen whether published manufacturer heating data covers the planned outdoor design point) rather than restating the tool name. It is clear enough to distinguish from generic datasheet lookups, though it never explicitly contrasts itself with close siblings such as klima_heizfunktion_datenblatt_nachweis.

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?

The phrase 'for the planned outdoor conditions' hints at the scenario, but there is no explicit when-to-use, no prerequisite (e.g. that the verified minimum operating limit must already be confirmed), and no statement of when this check is unnecessary or which sibling handles the adjacent task.

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