Skip to main content
Glama

getecoback-raumklima

heizwaesche_hilfe_zeitgewinn_mehrstrom_budget

Read-only

Einen belegten Zeitgewinn mit separat erfasstem Mehrstrom je gewünschter Zeiteinheit vergleichen — Evaluate an observed time saving against a household marginal energy budget.

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": {
      "gleicher_endzustand": "<gleicher_endzustand>",
      "ohne_min": "<ohne_min>",
      "mit_min": "<mit_min>",
      "ohne_kwh": "<ohne_kwh>",
      "mit_kwh": "<mit_kwh>",
      "grenzwert_kwh_je_stunde": "<grenzwert_kwh_je_stunde>"
    },
    "name": "heizwaesche_hilfe_zeitgewinn_mehrstrom_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
mit_kwhYesGesamtenergie einschließlich Hilfe.
mit_minYesGemessene Dauer mit zusätzlicher Hilfe.
ohne_kwhYesGesamtenergie ohne Hilfe.
ohne_minYesGemessene Dauer ohne zusätzliche Hilfe.
gleicher_endzustandYesSind Trockenmasse, Startfeuchte und tatsächlich kontrollierter Endzustand vergleichbar, und ist der Strom aller beteiligten Geräte erfasst?
grenzwert_kwh_je_stundeYesEigene Grenze zusätzlichen Stroms je beobachteter gesparter Stunde.

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 the tool as readOnly and closed-world, i.e. a pure computation, so the description's main additional duty is to explain the internal logic and result. It conveys that the comparison is normalized per time unit against a marginal energy budget, but never says how the extra energy is derived (mit_kwh minus ohne_kwh) or that gleicher_endzustand acts as a validity gate that can invalidate the comparison. With no output schema, the missing description of the returned verdict is a real gap.

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, German then English, with the verb and the comparison partner front-loaded and no filler. The bilingual duplication costs a little space but is an intentional accessibility choice, not padding.

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?

The tool is a six-parameter, all-required computation with no output schema, so the description needs to carry the interpretation of the result and the role of the validity flag. It does neither, leaving an agent able to call it but not to anticipate what a successful or gated outcome looks like.

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 six parameters are required with documented bounds and German descriptions, so the schema carries the burden and the baseline is 3. The description adds a little by framing mit_kwh as "separat erfasstem Mehrstrom" and implying a per-hour normalization, but it never clarifies how grenzwert_kwh_je_stunde interacts with the measured values or what gleicher_endzustand does to 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?

The description pairs a specific verb ("vergleichen") with concrete resources: an observed time saving, separately recorded extra energy, normalized per time unit, and a household marginal energy budget. An agent can tell this is an energy-budget verdict rather than a surcharge or cost verdict. It does not name or differentiate itself from near-siblings such as reiniger_zeitgewinn_gegen_aufpreis, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrasing "belegten Zeitgewinn mit separat erfasstem Mehrstrom je gewünschter Zeiteinheit" signals that the tool applies when both durations and both energy readings have been measured. There is no explicit when-to-use, when-not-to-use, or statement of which sibling to pick for a cost-based comparison instead.

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