Skip to main content
Glama

getecoback-climate-weather

heizwaesche_zwei_trockenziele_veraenderter_endpunkt

Read-only

Bei Wechsel vom schnellen Zwischenziel zum gewünschten Endzustand bereits gemessene Energie getrennt halten — Separate a documented partial drying target from the final one.

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": {
      "dieselbe_ladung": "<dieselbe_ladung>",
      "zwischen_min": "<zwischen_min>",
      "ende_min": "<ende_min>",
      "zwischen_kwh": "<zwischen_kwh>",
      "ende_kwh": "<ende_kwh>",
      "endziel_bestaetigt": "<endziel_bestaetigt>"
    },
    "name": "heizwaesche_zwei_trockenziele_veraenderter_endpunkt"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_kwhYesKumulierte Energie beim Endzustand.
ende_minYesZeitpunkt der dokumentierten endgültigen Stufe.
zwischen_kwhYesKumulierte Energie am Zwischenzustand.
zwischen_minYesZeitpunkt der zuerst dokumentierten Zwischenstufe.
dieselbe_ladungYesSind Zwischen- und Endwert am selben unveränderten Satz Textilien und derselben Stromgrenze belegt?
endziel_bestaetigtYesWurde der Endzustand für diese konkrete Ladung wirklich bestätigt?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the semantic rule that intermediate and final readings must be kept apart, but says nothing about how the result behaves when dieselbe_ladung or endziel_bestaetigt is false — error, warning, or rejected record — which is the main behavioral unknown.

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 tight clauses with the trigger condition front-loaded and no padding; the German half and English half are redundant but that redundancy is deliberate bilingualism rather than waste. Slight deduction because the shortened phrasing ("getrennt halten") is dense enough to be ambiguous on first read.

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?

With six required fields, no output schema, and a read-only operation, the description does need to convey what the call yields or validates, and it does not. It gives the conceptual rule (keep the two measurements distinct) but not the outcome, which leaves an agent guessing about return values and about the role of the two boolean confirmation flags.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Not applicable at the level of added meaning: schema description coverage is 100% with six fully documented parameters, so the schema carries the semantics and the description needs only frame the operation. It correctly frames it as separating a between-state energy from the end-state energy, matching zwischen_kwh/ende_kwh versus zwischen_min/ende_min.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an action ("bereits gemessene Energie getrennt halten" / "Separate a documented partial drying target from the final one"), so the agent gets a verb and a resource. But the resource is abstract (measured energy vs. a drying target) and the phrasing never states concretely what the tool produces, leaving the purpose only inferable from the parameter names in the schema.

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?

A triggering condition is given ("Bei Wechsel vom schnellen Zwischenziel zum gewünschten Endzustand"), which implies when the tool applies. There is no explicit statement of when not to use it and no named alternative among the many similarly-named sibling tools, so the routing guidance is only implied.

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