Skip to main content
Glama

getecoback-raumklima

standby_steckdosengruppe_abschalten

Read-only

Nettoeinsparung einer abschaltbaren Gerätegruppe mit Eigenverbrauch der Steuerung prüfen. — Work out whether a safely switchable standby group saves energy after controller overhead.

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": {
      "standby_w": "<standby_w>",
      "abschaltzeit_h_tag": "<abschaltzeit_h_tag>",
      "steuerung_w": "<steuerung_w>",
      "arbeit": "<arbeit>",
      "geeignet": "<geeignet>"
    },
    "name": "standby_steckdosengruppe_abschalten"
  }
}

Input Schema

NameRequiredDescriptionDefault
arbeitYesBrutto-Arbeitspreis in €/kWh.
geeignetYesAlle Geräte dürfen laut Anleitung vollständig vom Strom getrennt werden und müssen keine Aufgaben im Hintergrund erledigen.
standby_wYesGemessene gemeinsame Ruhe-Wirkleistung in Watt.
steuerung_wYesMittlere Dauerleistung der Schaltsteuerung in Watt. Bei einer mechanisch abschaltbaren Leiste ohne Eigenverbrauch 0.
abschaltzeit_h_tagYesSichere Abschaltdauer in Stunden pro Tag.

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. The description adds only that the calculation is net of controller overhead (gross standby power minus control consumption), and says nothing about the result's unit, time basis, or sign convention.

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 German sentence is front-loaded and functional, but the English second half is a near-verbatim translation that adds no new information. Two sentences where one would have sufficed.

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 read-only, five-required-parameter calculation with no output schema, the description conveys the decision question but omits the result's unit and time basis (per day, per year) and the annualization over abschaltzeit_h_tag, which the agent cannot recover from any structured field.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description nevertheless adds real meaning by framing the computation as net savings after controller overhead, which corresponds to steuerung_w and signals that standby_w is gross rather than net. It stops short of tying semantics to the economic parameter (arbeit) or the safety gate (geeignet).

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 states a specific verb and resource: check the net savings of a switchable device group including controller overhead. An agent can tell this is a calculation/decision tool, though it does not name or differentiate itself from any sibling.

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 implied: you have a standby group with measured standby power, a switch controller, and want to know whether shutting it off still nets a saving. There is no explicit when-to-use/when-not guidance and no named alternative among the many sibling calculation tools.

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