Skip to main content
Glama

getecoback-raumklima

heizenergie_volumen_faktorstaffel

Read-only

Zwei getrennte Volumenzeiträume mit den jeweils belegten Umrechnungsfaktoren in kWh zusammenführen — Reconcile separately applied heat-billing volume factors.

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": {
      "volumen_a_m3": "<volumen_a_m3>",
      "volumen_b_m3": "<volumen_b_m3>",
      "faktor_a": "<faktor_a>",
      "faktor_b": "<faktor_b>",
      "beleg_kwh": "<beleg_kwh>",
      "abschnitte_bestaetigt": "<abschnitte_bestaetigt>"
    },
    "name": "heizenergie_volumen_faktorstaffel"
  }
}

Input Schema

NameRequiredDescriptionDefault
faktor_aYesBelegter Gesamtfaktor der ersten Teilperiode in kWh/m³.
faktor_bYesBelegter Gesamtfaktor der zweiten Teilperiode in kWh/m³.
beleg_kwhYesIn der Rechnung ausgewiesene kWh über beide Teilperioden.
volumen_a_m3YesAbgelesenes Volumen der ersten Teilperiode in m³.
volumen_b_m3YesAbgelesenes Volumen der zweiten Teilperiode in m³.
abschnitte_bestaetigtYesSind die zugeordneten Teilperioden lückenlos und überschneidungsfrei?

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds that this is a reconciliation of two period factors, but it does not disclose how a false abschnitte_bestaetigt is handled (rejection vs. warning) or what the computed result represents.

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 tightly packed sentence with the core operation front-loaded, followed by a bilingual gloss. No filler, though the em-dash duplication of the same content in two languages is slightly redundant for an agent reader.

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 pure computation tool with no output schema, the description should say what the agent gets back (reconciled kWh total vs. difference of the two period products). That return-value gap and the undisclosed behavior of the confirmation flag leave it only adequately specified.

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 including their units and bounds are already documented, giving a baseline of 3. The description only reinforces that volumen_a/b pair with faktor_a/b over two periods; it adds nothing about the gating role of abschnitte_bestaetigt or how beleg_kwh is used as a check.

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 verb (zusammenführen/reconcile) and a specific resource (two separate volume periods with their applied kWh/m³ conversion factors). The German/English pairing makes the intent unambiguous, though the phrasing is dense and the resulting artifact (a reconciled delta) is only implied.

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 by 'separately applied' factors (split billing periods), but there is no explicit when-to-use, when-not-to-use, or reference to any alternative sibling tool. Nothing tells the agent what to do when the periods are not contiguous.

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