Skip to main content
Glama

getecoback-climate-weather

spuelmaschine_handspuelen_kosten

Read-only

Spülmaschine und Handwäsche für dieselbe Geschirrmenge inklusive Warmwasser vergleichen. — Compare dishwashing costs for the same load with hot water and electricity.

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": {
      "maschine_kwh": "<maschine_kwh>",
      "maschine_l": "<maschine_l>",
      "hand_l": "<hand_l>",
      "temperaturhub_c": "<temperaturhub_c>",
      "waermefaktor": "<waermefaktor>",
      "strom_eur_kwh": "<strom_eur_kwh>",
      "waerme_eur_kwh": "<waerme_eur_kwh>",
      "wasser_eur_m3": "<wasser_eur_m3>"
    },
    "name": "spuelmaschine_handspuelen_kosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
hand_lYesWarmwasser für das Handspülen derselben Geschirrmenge in Litern.
maschine_lYesMaschinenwasser in Litern pro Programm.
maschine_kwhYesStrom für ein vollständiges Maschinenprogramm bei Kaltwasseranschluss.
waermefaktorYesNutzwärme je Energieeinheit der Warmwasserbereitung. Beispiel: Wirkungsgrad 0,85.
strom_eur_kwhYesBrutto-Strompreis in €/kWh für die Maschine.
wasser_eur_m3YesKombinierter Wasser- und Abwasserpreis in €/m³.
waerme_eur_kwhYesBrutto-Preis des Energieeinsatzes zur Warmwasserbereitung in €/kWh.
temperaturhub_cYesUnterschied zwischen Zulauf- und Handspültemperatur in °C.

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 annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed calculation. The description adds that hot-water heating and electricity are part of the cost model, which explains why temperature-lift and heat-factor inputs exist. It says nothing about what the result looks like (currency totals, per-load breakdown), and there is no output schema to cover that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and short, but the German sentence and the English sentence are near-duplicate restatements rather than complementary information. Half the text is translation overhead, leaving little room for substantive guidance.

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

Completeness4/5

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

For a pure, side-effect-free calculator with eight fully documented required parameters and no output schema, the description covers purpose and cost scope adequately. The residual gap is that the shape of the returned comparison is never hinted at, which matters given the absence of an output schema.

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 every parameter carries a unit and bound, so the schema already does the heavy lifting. The description only loosely corroborates the model by mentioning hot water and electricity; it adds no interpretation of the individual inputs beyond what the schema states. 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 concrete operation on a concrete resource: comparing dishwasher versus handwashing costs for the same load of dishes. A reader immediately knows the output is a cost comparison, not a measurement or a device-selection aid. No sibling covers dishwashing costs, so explicit differentiation is unnecessary.

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 statement of when to reach for this tool versus alternatives, no prerequisites (e.g., that all eight inputs must be known up front), and no exclusions. Usage must be inferred purely from the verb 'compare'.

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