Skip to main content
Glama

getecoback-raumklima

stromverlauf_budgetgrenze_ablesungen

Read-only

Ermitteln, zwischen welchen bestätigten Ablesungen der kumulierte Verbrauch erstmals das eigene Budget erreichte — Bracket the first threshold crossing in a monotone three-reading history.

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": {
      "erster_kwh": "<erster_kwh>",
      "zweiter_kwh": "<zweiter_kwh>",
      "dritter_kwh": "<dritter_kwh>",
      "grenze_kwh": "<grenze_kwh>",
      "monoton_belegt": "<monoton_belegt>"
    },
    "name": "stromverlauf_budgetgrenze_ablesungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
erster_kwhYesErster Verbrauchsstand relativ zum Beginn des Budgets.
grenze_kwhYesGewählte positive Budgetgrenze in kWh.
dritter_kwhYesDritter Verbrauchsstand auf derselben relativen Skala.
zweiter_kwhYesZweiter Verbrauchsstand auf derselben relativen Skala.
monoton_belegtYesEinheit, Register und durchgehend kumulierende Verbrauchsmessung sind bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/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's remaining job is to explain the computation, which it does by stating it brackets (not interpolates) the first crossing and that history must be monotone. It does not say what happens when no crossing exists, which is a real behavioral gap for a threshold tool.

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 no padding, and the bracketing semantics arrive before any qualifiers. The verbatim German/English duplication communicates the same content twice, which is mild waste but keeps it short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a pure read-only computation the description conveys the inputs' meaning, the monotonicity precondition, and the bracketing output concept, so nothing essential is missing. The absence of an output schema means the exact return shape (bracket endpoints, no-crossing case) could have been spelled out but is at least implied.

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 every parameter including 'monoton_belegt' is already documented in the schema, giving a baseline of 3. The description adds only the ordering constraint (a monotone three-reading sequence feeding a cumulative budget) and no extra meaning for the individual kWh fields.

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 – bracketing the first budget-threshold crossing within a strictly three-reading cumulative history – which pins down scope far beyond the generic tool name. It is unmistakably distinct from the sibling set, though it never names an alternative to route against.

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 context is implied rather than stated: 'bestätigten Ablesungen' and the required 'monoton_belegt' flag signal that readings must be confirmed as a continuous cumulative register before calling. There is no explicit when-not guidance, no mention of what to do if the crossing occurs before the first or after the third reading, and no named alternative for non-monotone data.

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