Skip to main content
Glama

getecoback-raumklima

kuehlschrank_wechsel_geraetepaar_labelvergleich_bestand

Read-only

Vergleicht die Jahresenergie beim Wechsel zur Kühlkombi und berücksichtigt, ob der separate Gefrierschrank weiterläuft — Reconcile a one-versus-two cabinet replacement energy scenario

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": {
      "alt_kuehl_kwh": "<alt_kuehl_kwh>",
      "alt_gefrier_kwh": "<alt_gefrier_kwh>",
      "neu_kombi_kwh": "<neu_kombi_kwh>",
      "gefriergeraet_danach": "<gefriergeraet_danach>",
      "lasten_gleich_und_belegt": "<lasten_gleich_und_belegt>"
    },
    "name": "kuehlschrank_wechsel_geraetepaar_labelvergleich_bestand"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_kuehl_kwhYesVergleichbar deklarierte oder eigens ermittelte Jahres-kWh des ersetzten Kühlschranks.
neu_kombi_kwhYesJahres-kWh der Kombi auf derselben belegten Vergleichsgrundlage.
alt_gefrier_kwhYesJahres-kWh des vorhandenen separaten Gefriergeräts auf derselben belegten Vergleichsgrundlage.
gefriergeraet_danachYesZustand des separaten Gefriergeräts nach dem Umstieg.
lasten_gleich_und_belegtYesFachbedarf nach der Umstellung und einheitliche Vergleichsgrundlage sind belegt und zusätzlicher eigener Betrieb ist berücksichtigt.

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, and the verb 'Vergleicht' is consistent with a pure computation, so there is no contradiction. Beyond that the description adds only the reminder that the separate freezer's continued operation is factored in; it says nothing about what a result looks like or what the reconciliation actually produces.

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?

Two compact sentences with the German statement followed by a short English gloss, and the scenario constraint is front-loaded. Nothing is wasted, though mixing languages in a single field is slightly less clean than one consistent phrasing.

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?

There is no output schema, so the description bears the burden of indicating the return value, and it never says whether the result is an absolute delta in kWh, a saving, or a verdict. For a five-parameter required-all calculation tool the inputs are well covered, but the outcome remains 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% and all five parameters are documented in the schema, including the enum values for the freezer's post-switch state. The description's clause about whether the separate freezer keeps running paraphrases that parameter but adds no units, aggregation logic, or comparison-basis details 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 operation and resource: comparing annual energy ('Jahresenergie') when switching to a fridge-freezer combination, plus the explicit scope of a one-versus-two cabinet scenario. That scenario framing separates it from the many single-cabinet siblings (label comparison, efficiency class, temperature protocol), though it does not name a sibling directly.

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 English clause 'Reconcile a one-versus-two cabinet replacement energy scenario' implies the applicable situation, and the note about the separate freezer still running signals the decision it supports. There is no explicit when-not guidance and no named alternative for the single-cabinet case, leaving the agent to infer the boundary against siblings like the label-comparison tool.

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