Skip to main content
Glama

getecoback-climate-weather

stromtarif_niedertarif_mindestanteil

Read-only

Benötigten Anteil des Verbrauchs im günstigen Zeitfenster gegenüber einem Einheitstarif bestimmen. — Find how much consumption must fall in the low-rate band to match a flat offer.

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": {
      "jahres_kwh": "<jahres_kwh>",
      "grund_flat": "<grund_flat>",
      "preis_flat": "<preis_flat>",
      "grund_zeit": "<grund_zeit>",
      "preis_hoch": "<preis_hoch>",
      "preis_niedrig": "<preis_niedrig>"
    },
    "name": "stromtarif_niedertarif_mindestanteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
grund_flatYesJahresgrundpreis des Einheitstarifs.
grund_zeitYesJahresgrundpreis des Zweizeit-Tarifs.
jahres_kwhYesErwarteter Jahresverbrauch in kWh.
preis_flatYesBrutto-€/kWh des Einheitstarifs.
preis_hochYesBrutto-€/kWh außerhalb des günstigen Fensters.
preis_niedrigYesBrutto-€/kWh im günstigen Fenster.

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, consistent with a pure offline calculation, so no contradiction exists. The description adds useful context that the output is a comparison threshold against a flat offer, but it says nothing about what the result represents when the flat tariff is already cheaper, nor about the form of the returned value.

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, German followed by an English restatement, with the core purpose front-loaded and no filler. The bilingual duplication is the only redundancy, and it is defensible for a mixed-language catalog.

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?

There is no output schema, so the description carries the burden of explaining the return value, and it only hints at it ('how much consumption must fall in the low-rate band'). For a six-parameter calculator whose result interpretation matters, it should state whether the answer is a percentage, kWh amount, or break-even flag.

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%, so all six parameters are already documented in the schema, establishing a baseline of 3. The description adds conceptual framing that pairs the flat parameters against the high/low-rate parameters, but gives no additional detail on units, ranges, or how the two grund/preis groups interact.

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 concrete computation: the share of consumption that must land in the low-rate band for a two-rate tariff to match a flat offer. That is a specific verb-plus-result, not a restatement of the name. It stops short of distinguishing itself from nearby tariff tools such as stromtarif_verbrauchsschwelle, which an agent could easily confuse it with.

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 framing 'gegenüber einem Einheitstarif' implies the use case (flat vs. time-of-use comparison) strongly enough that an agent can infer when it applies. However, no explicit when-to-use, when-not-to-use, or alternative sibling is named, so selection among the many stromtarif_* tools is left to inference.

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