Skip to main content
Glama

getecoback-climate-weather

geraeteaufpreis_strompreisband

Read-only

Prüfen, ob sich ein Geräteaufpreis bei niedrigen und hohen eigenen Strompreisen innerhalb der Nutzungsfrist ausgleicht — Test the purchase premium across a range of energy prices.

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": {
      "aufpreis_eur": "<aufpreis_eur>",
      "ersparnis_kwh_jahr": "<ersparnis_kwh_jahr>",
      "jahre": "<jahre>",
      "tarif_tief": "<tarif_tief>",
      "tarif_hoch": "<tarif_hoch>"
    },
    "name": "geraeteaufpreis_strompreisband"
  }
}

Input Schema

NameRequiredDescriptionDefault
jahreYesAngenommene gleich lange Nutzungszeit in Jahren.
tarif_hochYesEigenes oberes Szenario in Euro pro kWh.
tarif_tiefYesEigenes unteres Szenario in Euro pro kWh.
aufpreis_eurYesAufpreis des sparsameren Geräts in Euro.
ersparnis_kwh_jahrYesVergleichbare jährliche kWh-Ersparnis.

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 computation and the description does not need to restate that. What the description does add is the two-scenario framing (low vs. high price band), which is genuine behavioral context. However, it never says what the tool actually returns — a yes/no payback verdict, a breakeven price, a per-year table — which matters for a pure calculation tool with 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?

One front-loaded German sentence followed by a short English gloss; the purpose is stated immediately with no filler. The bilingual duplication is mildly redundant but defensible for a German-domain tool, and nothing is buried.

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 required inputs are fully specified in the schema with units and ranges, and annotations cover the safety profile, so the description does not need to repeat those. The remaining gap is the return value: with no output schema and no description of the result, an agent cannot predict whether it gets a boolean, a breakeven year, or a comparison table.

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 with units and bounds, making 3 the baseline. The description adds conceptual meaning by tying the calculation to a low and high price band (tarif_tief/tarif_hoch) and to the usage period (jahre), but it never mentions the annual kWh savings input (ersparnis_kwh_jahr), which is arguably the core driver of the calculation.

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 states a concrete verb (Prüfen / test) and a concrete subject: whether a device purchase premium (Geräteaufpreis) amortizes within the usage period at low and high electricity prices. That is far more specific than the tool name alone. It does not differentiate itself from any sibling, but the sibling list is a broad topic catalog rather than a set of near-duplicates, so the omission is minor.

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 is only implied: an agent can infer this is for payback/breakeven checks on a more efficient appliance. There is no explicit statement of when to pick this over another tool, no prerequisites, and no exclusions. Adequate but with clear gaps.

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