Skip to main content
Glama

getecoback-climate-weather

klima_kuehlleistung_einheit_abgleich

Read-only

Zwei Kühlleistungen aus kW und BTU/h auf dieselbe Einheit bringen — Normalize two published cooling capacity figures, with a test-condition gate.

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": {
      "leistung_a_kw": "<leistung_a_kw>",
      "leistung_b_btuh": "<leistung_b_btuh>",
      "gleicher_pruefpunkt": "<gleicher_pruefpunkt>"
    },
    "name": "klima_kuehlleistung_einheit_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
leistung_a_kwYesKühlleistung A in Kilowatt.
leistung_b_btuhYesKühlleistung B in BTU pro Stunde, nicht bloß BTU Energie.
gleicher_pruefpunktYesGelten dieselbe Prüfmethode und derselbe Betriebspunkt?

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 notable behavioral detail that a test-condition gate exists, but does not say what happens when 'gleicher_pruefpunkt' is false — whether conversion is refused, flagged, or returned with a caveat.

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 compact bilingual sentence with the operation front-loaded and the gate condition appended. Every clause carries information; the German/English duplication is the only minor redundancy.

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?

With no output schema, the description should indicate what the normalized result looks like (single unit? which one? both values plus a comparability verdict?). Given three required parameters and a gate concept, the definition is adequate but leaves the return contract and gate-failure behavior unspecified.

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 three parameters are already documented in the schema, including the useful clarification that BTU/h is power not energy. The description adds only the framing of 'two published figures', not new parameter-level meaning.

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 operation: converting two published cooling-capacity figures (kW and BTU/h) to a common unit, plus a test-condition gate. It is distinguishable from sibling tools like klima_waermeabgabe_kreislauf or klima_effizienzlabel_vergleichen, though it does not explicitly name a sibling it replaces.

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 'with a test-condition gate' and the required boolean imply usage requires confirming identical test method and operating point, but the description never states when to use this tool versus alternatives or what to do when the gate fails.

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