Skip to main content
Glama

getecoback-climate-weather

strompreis_grenzblock_kostenband

Read-only

Die Kosten einer ungeteilten Verbrauchsmenge direkt am Tarifwechsel eingrenzen — Bound charges for a metered block that straddles a known rate boundary.

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": {
      "vor_sicher_kwh": "<vor_sicher_kwh>",
      "danach_sicher_kwh": "<danach_sicher_kwh>",
      "grenzblock_kwh": "<grenzblock_kwh>",
      "vor_cent_kwh": "<vor_cent_kwh>",
      "danach_cent_kwh": "<danach_cent_kwh>"
    },
    "name": "strompreis_grenzblock_kostenband"
  }
}

Input Schema

NameRequiredDescriptionDefault
vor_cent_kwhYesBelegter variabler Preis vor der Grenze in Cent/kWh.
grenzblock_kwhYesNur der beiden Zeitfenstern noch nicht zuordenbare, separat gemessene Verbrauchsblock.
vor_sicher_kwhYesMenge vollständig vor der Preisgrenze.
danach_cent_kwhYesBelegter variabler Preis nach der Grenze in Cent/kWh.
danach_sicher_kwhYesMenge vollständig nach der Preisgrenze.

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 safety is covered. The description adds one genuinely useful behavioral fact beyond that: the result is a bounded band ('eingrenzen', 'Bound charges'), i.e. a range rather than a single exact cost, because the block is undivided. It does not say how the band is formed or what happens with degenerate inputs.

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?

A single front-loaded sentence with the core concept first and a bilingual restatement that aids matching without adding new claims. No filler, though the English half is largely a translation rather than additional information.

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?

All five parameters are documented and the tool is a read-only calculation with no output schema, so the description carries the burden of indicating the return shape. 'Kostenband'/'Bound charges' hints at a range, but the description never states whether the result is a min/max pair, a total in cents, or how the undivided block is distributed — a gap for a computational tool whose output an agent must interpret.

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 the five required numeric parameters (vor_sicher_kwh, danach_sicher_kwh, grenzblock_kwh, vor_cent_kwh, danach_cent_kwh) are already fully documented in the schema. The description reinforces the concept of an unresolved residual block plus two certain quantities but adds no units, rounding, or constraint semantics beyond the schema.

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 specific operation: bounding the cost of an undivided (ungeteilten) consumption block that straddles a known rate boundary, with both German and English formulations. It is concrete enough to distinguish a straddling-block cost-range calculation from sibling tools such as strompreis_zeitreihe_vollstaendigkeit_beleg or strompreis_zwei_geraete_ruhefenster, though it never names an alternative explicitly.

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?

Applicability is implied by the phrase 'einer ungeteilten Verbrauchsmenge ... am Tarifwechsel' — use it when a measured block cannot be cleanly assigned to the before/after rate windows. There is no explicit when-to-use/when-not guidance, no statement of prerequisites, and no routing to sibling tools for the splittable case.

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