Skip to main content
Glama

getecoback-climate-weather

geraetewechsel_rechnen

Read-only

Altgerät behalten oder ersetzen — Compare the cost of keeping an appliance with replacing it.

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": {
      "oldKwh": "<oldKwh>",
      "newKwh": "<newKwh>",
      "purchase": "<purchase>",
      "years": "<years>",
      "price": "<price>"
    },
    "name": "geraetewechsel_rechnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesEigener Strompreis in EUR/kWh.
yearsYesVergleichszeitraum in Jahren.
newKwhYesJahresverbrauch Ersatzgerät in kWh.
oldKwhYesJahresverbrauch Altgerät in kWh.
purchaseYesAnschaffungskosten in Euro.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations only declare readOnlyHint and openWorldHint, so the lower bar applies, yet the description adds nothing about the calculation itself — no mention of whether energy price escalation, total cost over 'years', or amortization is modeled. For a computation tool with no output schema, the result shape (cost difference, savings, break-even) is left entirely unexplained.

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 short clauses with zero padding and the decision framing first. The German title phrase and the English sentence convey largely the same idea, which is slight redundancy, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five required numeric parameters and a computational purpose demand more than a one-line purpose statement: there is no output schema and no description of what the returned figure represents or its units. An agent knows what the tool is about but not what it will get back.

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%, with each of the five parameters documented in German (consumption, purchase cost, period, price). The description adds no meaning 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 description names a specific operation — comparing the cost of keeping an old appliance versus replacing it — with the decision framing 'Altgerät behalten oder ersetzen' front-loaded. An agent can tell this is a cost-comparison calculator, though it does not distinguish itself from nearby tools such as geraet_wahl or arbeitszimmer_abwaerme_vergleich.

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 framing 'keep or replace' implies the decision context in which the tool applies, but there is no explicit statement of when to use it versus sibling comparison tools, and no mention of prerequisites such as needing the old device's annual consumption.

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