Skip to main content
Glama

getecoback-climate-weather

klima_effizienzlabel_vergleichen

Read-only

Kühl-Effizienzkennzahlen für Monoblock und Split auf Vergleichbarkeit prüfen — Compare EER or SEER figures only on the same stated test basis.

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": {
      "index_a": "<index_a>",
      "index_b": "<index_b>",
      "wert_a": "<wert_a>",
      "wert_b": "<wert_b>",
      "gleiche_pruefbasis": "<gleiche_pruefbasis>"
    },
    "name": "klima_effizienzlabel_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
wert_aYesVeröffentlichter Kühl-Wirkungsgrad A in W/W, sofern bekannt. Bei unbekannter Kennzahl 0.
wert_bYesVeröffentlichter Kühl-Wirkungsgrad B in W/W, sofern bekannt. Bei unbekannter Kennzahl 0.
index_aYesKühl-Kennzahl A, falls bekannt.
index_bYesKühl-Kennzahl B, falls bekannt.
gleiche_pruefbasisYesJeweils derselbe Teststandard, Klimabezug und Typ der Kühlleistungsangabe?

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 and the description only needs to add comparison semantics. It adds the key constraint that mismatched test bases invalidate a comparison, which is real behavioral context. However, with no output schema, it never says what the tool returns (a verdict, a warning, a normalized pair), which is the main missing behavioral fact.

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?

Bilingual but tightly parallel: the scope of the check comes first, then the validity constraint. Two sentences, no filler, nothing repeated that the schema already states. Slightly verbose only because the same content is expressed twice.

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 five-parameter, fully required, read-only checker with no output schema, the definition should at minimum indicate the shape of the result and what happens when gleiche_pruefbasis is false. It covers the input discipline well but stops short of describing the outcome, leaving a real gap for calling correctly.

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% and each of the five required parameters is documented in the schema, including the enum values for index_a/index_b and the '0 if unknown' convention for values. The description only reinforces gleiche_pruefbasis via the 'same stated test basis' phrasing and adds no new syntax or interpretation beyond the schema, 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 German and English halves both name a specific action (prüfen / compare) and a specific resource (EER/SEER cooling efficiency figures for Monoblock and Split units), not a restatement of the tool name. It is clear enough to distinguish from evaluation siblings such as klima_abkuehltest_auswerten, though no sibling is explicitly named as an alternative.

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 clause 'only on the same stated test basis' implies the gating condition — comparisons are only valid when test standard, climate reference and capacity type match — but that reads as a validity rule rather than explicit when-to-use guidance. There is no statement of when NOT to call it and no named alternative tool for adjacent tasks like label reconciliation.

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