Skip to main content
Glama

getecoback-climate-weather

stromsparplan_massnahmen_ueberlappung

Read-only

Gemeinsamen Einsparanteil zweier Maßnahmen vor einem Zielvergleich nur einmal zählen — Avoid double-counting overlapping measured electricity 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": {
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "ueberlappung_kwh": "<ueberlappung_kwh>",
      "ziel_kwh": "<ziel_kwh>"
    },
    "name": "stromsparplan_massnahmen_ueberlappung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGeschätzter oder gemessener Effekt von Maßnahme A in kWh.
b_kwhYesGeschätzter oder gemessener Effekt von Maßnahme B in kWh.
ziel_kwhYesEigenes Einsparziel desselben Zeitraums in kWh.
ueberlappung_kwhYesGemeinsamer Anteil beider Effekte im selben Zeitraum in kWh.

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?

readOnlyHint=true and openWorldHint=false already establish that this is a safe, closed-world computation. The description adds the domain intent but says nothing about how overlap is treated, such as whether it is subtracted, clamped against ziel_kwh, or returned as an over-count. That is the main behavioral unknown, but with annotations carrying the safety profile a 3 is fair.

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 clauses that lead with the rule and follow with a translation, so the intent is clear upfront. The German and English sentences are near-duplicates, which is harmless but not free.

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 four-parameter calculation with no output schema, the reader knows the inputs but not the shape of the answer. The definition never says whether the result is a corrected total, a remaining target, or a boolean, so it is incomplete for a compute tool.

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 coverage is 100%, so every parameter has its own description and the description adds no format or unit detail. Baseline 3 applies.

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 concrete operation on a concrete quantity: the shared savings share of two measures should be counted only once. This separates the tool from per-measure tools, but it never says what the tool returns, so the verb is inferential.

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?

"vor einem Zielvergleich" implies a usage moment, and "nur einmal zählen" implies double counting should be avoided. No explicit when-not, no prerequisites, and no mention of the sibling overlap tools such as fassadenbeschattung_zeitfenster_ueberlappung.

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