Skip to main content
Glama

getecoback-climate-weather

klima_heizfunktion_datenblatt_nachweis

Read-only

Heizfunktion anhand der Gerätedokumentation als Wärmepumpe oder Direktheizung einordnen — Verify the documented heating principle in a reversible AC.

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": {
      "dokument": "<dokument>",
      "temperaturpunkt": "<temperaturpunkt>",
      "paarwerte": "<paarwerte>"
    },
    "name": "klima_heizfunktion_datenblatt_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
dokumentYesSpezifisch für den Heizbetrieb dokumentierte Technik.
paarwerteYesSind Heizleistung und Aufnahmewert am selben Punkt genannt?
temperaturpunktYesSind Außen- und Innentemperatur zum Heizleistungswert genannt?

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?

The readOnlyHint and openWorldHint annotations already establish that this is a closed-domain read operation, and the description does not contradict them. It adds that the classification is documentation-based, but it does not explain how the ambiguous 'unbekannt' case is treated or what the verification returns.

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 definition is a single compact sentence with the purpose front-loaded, and it contains no irrelevant detail. The bilingual German/English restatement is a minor redundancy but not a structural problem.

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 low-complexity read-only tool with three fully described required parameters and no output schema, the description is adequate about inputs and purpose. It does not explain the return value or how the three inputs combine into the final classification, which leaves a meaningful gap.

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 the enum for dokument and the boolean meanings of paarwerte and temperaturpunkt are already fully documented. The description mentions device documentation but does not add interpretation beyond the schema for the two boolean parameters.

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 states a specific verb and resource: classify the heating function from device documentation as a heat pump or direct electric heating. It is clear what the tool does, but it does not differentiate the tool from any sibling, such as klima_heizbetrieb_winterdaten_abgleich.

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 explicit when-to-use guidance, no conditions for choosing this tool over alternatives, and no exclusions. The closest guidance is implicit in the purpose statement: use it when device documentation must be interpreted for heating type.

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