Skip to main content
Glama

getecoback-climate-weather

wasserkocher_mehrmenge_szenario

Read-only

Zusätzlichen Strombedarf für regelmäßig zu viel eingefülltes Kochwasser abschätzen. — Estimate how much energy goes into repeatedly heating water you do not use.

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": {
      "eingefuellt_l": "<eingefuellt_l>",
      "benoetigt_l": "<benoetigt_l>",
      "temperaturhub_c": "<temperaturhub_c>",
      "wirkungsgrad": "<wirkungsgrad>",
      "vorgaenge": "<vorgaenge>",
      "strompreis": "<strompreis>"
    },
    "name": "wasserkocher_mehrmenge_szenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorgaengeYesZahl vergleichbarer Kochvorgänge im betrachteten Zeitraum.
strompreisYesBruttoarbeitspreis in €/kWh.
benoetigt_lYesBenötigte Menge in Litern, Hersteller-Mindestfüllung einhalten.
wirkungsgradYesAngenommener Anteil des Stroms, der das Wasser erwärmt, zwischen 0 und 1.
eingefuellt_lYesTatsächlich eingefüllte Menge in Litern.
temperaturhub_cYesGemessener Temperaturanstieg 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the non-destructive, offline character is covered. The description adds a genuine behavioural point beyond the schema: only the surplus water is costed, i.e. a marginal-delta calculation rather than total boiling energy. It discloses nothing about assumptions, rounding, or what the returned figure represents.

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 core purpose front-loaded; nothing is wasted on filler. The English second sentence largely restates the German one, which is mildly redundant but still short and readable.

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 six-parameter pure computation tool with no output schema, the description should say what the returned quantity is (kWh, €/year, both?) and roughly how the inputs combine. Neither is present, leaving an agent unable to describe the result to a user without calling the tool first.

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 ranges and units ('Bruttoarbeitspreis in €/kWh', 'Temperaturanstieg in °C', '0 bis 1'), so the schema carries parameter meaning on its own and the baseline of 3 applies. The description contributes no additional parameter-level guidance, not even how strompreis and wirkungsgrad shape the result.

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?

States a specific verb and resource: estimating the extra electricity demand caused by routinely overfilling kettle water. The wording 'Mehrmenge' / 'water you do not use' conveys the marginal-overfill basis, which is precise enough to distinguish it from an ordinary energy-consumption calculator. It does not name or differentiate against the other *_szenario siblings, keeping it short of a 5.

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?

The description says what is computed but never states when to prefer this over sibling scenario tools (e.g. heizwaerme_gradtag_szenario or dusche_waermeleistungsbedarf), nor any prerequisites or when-not conditions. Usage is only inferable from the name and the required parameters.

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