Skip to main content
Glama

getecoback-climate-weather

energielabel_skala_vergleichbarkeit

Read-only

Prüfen, ob zwei Effizienzklassen derselben Skala und Produktgruppe entstammen — Check comparability before using efficiency letters in a buying decision.

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": {
      "skala_a": "<skala_a>",
      "skala_b": "<skala_b>",
      "produktgruppe_gleich": "<produktgruppe_gleich>",
      "kennwertbasis_gleich": "<kennwertbasis_gleich>"
    },
    "name": "energielabel_skala_vergleichbarkeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
skala_aYesAuf Label A lesbare Skala.
skala_bYesAuf Label B lesbare Skala.
kennwertbasis_gleichYesBeziehen sich Zahlen auf dasselbe Programm beziehungsweise dieselbe Bezugsgröße?
produktgruppe_gleichYesBezieht sich das Label auf dieselbe Produktgruppe?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint=true and openWorldHint=false annotations already establish this as a side-effect-free, local computation, so the description only needs to add context. It frames the tool as a comparability gate ahead of a purchase, but says nothing about what verdict is returned or what happens when a scale is "unbekannt".

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 clause states the check, followed by a short purpose clause. The German/English duplication is slightly redundant but each half earns its place for a bilingual audience.

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?

All required parameters are documented and the safety profile is covered by annotations, so the agent can call it. However, with no output schema, the missing description of the returned comparability verdict leaves a real gap for a pure predicate tool.

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, including the two enums, are already documented in the input schema. The description restates the scale and product-group concepts but adds no interpretation of the parameters beyond the schema.

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 ("Prüfen") and a precise predicate: whether two efficiency classes come from the same scale and product group. That is clearly distinguishable from a value-matching tool such as energielabel_messwert_abgleichen, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete when-to-use context: run this before relying on efficiency letters in a buying decision. No when-not conditions or named alternatives are provided, so it stops short of full routing guidance.

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