Skip to main content
Glama

getecoback-raumklima

stromgruppe_vollstaendigkeitsrabatt_gesamtverlust

Read-only

Prüfen, ob das Verschieben eines Auftrags die Obergrenze für einen belegten Gruppenrabatt wieder einhält — Audit a documented threshold rebate separately from variable energy cost.

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": {
      "bisher_kwh": "<bisher_kwh>",
      "a_zusatz_kwh": "<a_zusatz_kwh>",
      "b_zusatz_kwh": "<b_zusatz_kwh>",
      "rabatt_bis_kwh": "<rabatt_bis_kwh>",
      "rabatt_euro": "<rabatt_euro>",
      "restbedingungen_bestaetigt": "<restbedingungen_bestaetigt>"
    },
    "name": "stromgruppe_vollstaendigkeitsrabatt_gesamtverlust"
  }
}

Input Schema

NameRequiredDescriptionDefault
bisher_kwhYesBereits bestätigte Verbrauchsmenge der gemeinsamen Abrechnung.
rabatt_euroYesBetrag des einmaligen Rabatts.
a_zusatz_kwhYesGemessene Zusatzmenge des im Zeitraum verbleibenden Auftrags A.
b_zusatz_kwhYesGemessene Energiemenge des innerhalb oder außerhalb des Abrechnungsfensters möglichen Auftrags B.
rabatt_bis_kwhYesBelegte Obergrenze für einen einmaligen, betragsfesten Gesamtrabatt.
restbedingungen_bestaetigtYesSind alle anderen Rabattbedingungen geprüft und jeweils erfüllt?

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 the agent knows this is a safe, closed-world read. The description adds the substantive context that the check concerns re-compliance with a documented cap after moving an order. It says nothing about what the check returns or what happens when the cap is violated, which matters since there is no output schema.

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 compact sentence that front-loads the check before the scope qualifier. The bilingual restatement after the dash is mildly redundant but does disambiguate the German terminology for an English-reading agent, so it mostly earns its place.

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 six-required-parameter read-only check with no output schema, the definition covers the intent well but leaves the result shape entirely unstated — an agent cannot tell whether it receives a boolean, a remaining headroom value, or a violation report. That is a meaningful gap for a pure verification 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 description coverage is 100%, so every parameter is already documented in the input schema and the baseline is 3. The description reinforces the semantics of the cap ('belegte Obergrenze') and the group rebate but adds no format, unit, or relationship guidance 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 check ('Prüfen, ob das Verschieben eines Auftrags die Obergrenze für einen belegten Gruppenrabatt wieder einhält'), which is far more than restating the name. It also distinguishes the scope from variable energy cost auditing. It stops short of naming any sibling tool, so differentiation is by topic only.

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 clause 'separately from variable energy cost' implies this is the audit to pick for rebate thresholds rather than cost calculations, which is useful implied guidance. There is no explicit when-not condition, no prerequisites, and no named alternative, so an agent must infer the boundary.

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