Skip to main content
Glama

getecoback-climate-weather

strombedarf_zwei_zeitfenster_aufschubkosten

Read-only

Zusätzlichen Warteverbrauch eines verschobenen Starts gegen den Tarifvorteil rechnen — Check whether standby energy during a delayed cycle offsets tariff savings.

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": {
      "lauf_kwh": "<lauf_kwh>",
      "frueh_eur_kwh": "<frueh_eur_kwh>",
      "spaet_eur_kwh": "<spaet_eur_kwh>",
      "warte_kwh": "<warte_kwh>",
      "warte_eur_kwh": "<warte_eur_kwh>"
    },
    "name": "strombedarf_zwei_zeitfenster_aufschubkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
lauf_kwhYesGemessene kWh eines vollständigen Laufs.
warte_kwhYesZusätzliche gemessene Standby-kWh der Verzögerung gegenüber sofortigem Start.
frueh_eur_kwhYesAktueller Endpreis für einen vollständigen frühen Lauf.
spaet_eur_kwhYesSpäterer Endpreis für einen vollständigen späten Lauf.
warte_eur_kwhYesVerbrauchsgewichteter Endpreis allein für den zusätzlichen Warteverbrauch.

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 clear. The description adds that this is a comparison calculation, but does not disclose the return value, sign convention, or assumptions; with annotations covering safety, a 3 is appropriate.

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 sentences, front-loaded with the purpose. The German and English versions duplicate the same information, which is slightly redundant though not harmful.

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 simple five-parameter calculation with a fully described schema and read-only annotations. However, no output schema exists and the description does not explain what the check returns or how to interpret the result, leaving a clear gap.

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 five parameters are individually documented. The description links Warteverbrauch with Tarifvorteil, but does not add per-parameter meaning or formula details beyond what the schema already provides.

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 calculation: additional standby consumption of a delayed start compared with tariff savings. The purpose is clear and conceptually distinct from generic load-shifting tools, but it does not explicitly name a sibling or state exclusions, so it is not 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?

The description implies the usage scenario—checking a delayed cycle against tariff savings—but gives no explicit when-to-use/when-not guidance or alternative-tool routing. It is adequate but leaves the agent to infer the decision context.

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