Skip to main content
Glama

getecoback-climate-weather

spuelprogramme_wasser_strom_zielkonflikt

Read-only

Zwei vollständig gemessene Spülprogramme auf Wasser- und Stromlimit prüfen und Zielkonflikte sichtbar machen — Check measured dishwashing cycles against independent water and electricity limits.

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": {
      "a_kwh": "<a_kwh>",
      "a_l": "<a_l>",
      "b_kwh": "<b_kwh>",
      "b_l": "<b_l>",
      "limit_kwh": "<limit_kwh>",
      "limit_l": "<limit_l>",
      "gleiche_aufgabe": "<gleiche_aufgabe>"
    },
    "name": "spuelprogramme_wasser_strom_zielkonflikt"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_lYesGemessener Wasserverbrauch je vollständigen Lauf A in Litern.
b_lYesGemessener Wasserverbrauch je vollständigen Lauf B in Litern.
a_kwhYesGemessener Energieverbrauch je vollständigen Lauf A.
b_kwhYesGemessener Energieverbrauch je vollständigen Lauf B.
limit_lYesEigenes Wasserlimit je gleichwertigem Spülgang.
limit_kwhYesEigenes Stromlimit je gleichwertigem Spülgang.
gleiche_aufgabeYesBeladung und erreichte Reinigungsaufgabe sind in beiden Messungen vergleichbar?

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, so the safety profile is covered and the description only needs to add context. It usefully stresses that the limits are independent (not a combined score) and that measurements must be complete, but it never says how the result is expressed or how a false 'gleiche_aufgabe' is handled. With no output schema and a 7-parameter analysis tool, that gap is meaningful.

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 sentence pair stating the check and its outcome with no filler. The German and English halves restate each other, which is defensible for a bilingual audience but is still duplication.

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 7 required inputs are documented in the schema and the read-only nature is annotated, so an agent can call it. Missing is what the 'Zielkonflikt' output looks like and how a false comparability flag changes the answer — the one thing an agent cannot infer from structured fields.

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 one of the 7 parameters carries a precise German explanation, so the schema does the heavy lifting and baseline 3 applies. The description adds only the notion of independent water and electricity limits, roughly duplicating the schema rather than clarifying units, threshold behavior, or the effect of the comparability flag.

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+resource ('Zwei vollständig gemessene Spülprogramme ... prüfen') plus the outcome ('Zielkonflikte sichtbar machen'), and 'gegen unabhängige Wasser- und Stromlimits' pins down the comparison. It is clearly distinct from the unrelated sibling tools, though it never names a sibling it is not.

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?

Usage is only implied: the phrase 'vollständig gemessene' signals the prerequisite that both runs must be fully measured, and 'gleiche_aufgabe' implies comparability is required. There is no explicit when-to-use/when-not, no statement of what happens if the runs are not comparable, and no named alternative.

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