Skip to main content
Glama

getecoback-raumklima

strombudget_maximaler_arbeitspreis

Read-only

Preisobergrenze für ein Eurobudget bei fest geplantem Verbrauch und Gebühren bestimmen — Compute the maximum all-in variable rate a fixed consumption budget can absorb.

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": {
      "budget_eur": "<budget_eur>",
      "plan_kwh": "<plan_kwh>",
      "fixkosten_eur": "<fixkosten_eur>",
      "angebot_eur_kwh": "<angebot_eur_kwh>"
    },
    "name": "strombudget_maximaler_arbeitspreis"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_kwhYesEingeplanter Verbrauch in diesem Zeitraum.
budget_eurYesGesamtbudget des Betrachtungszeitraums in Euro.
fixkosten_eurYesAlle festen, auf denselben Zeitraum entfallenden Gebühren in Euro.
angebot_eur_kwhYesBekannter alternativer Brutto-Arbeitspreis in Euro pro kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 safety profile is covered. The description adds that this is a pure forward computation over a fixed plan with fees, which clarifies it returns a derived rate rather than reading live market data. It does not disclose whether the negative lower bound of angebot_eur_kwh yields a valid comparison result or what the numeric output looks like, so the added value is moderate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states the ceiling computation and its constraints before the English restatement. The bilingual pairing costs some length but is the same content, and there is no filler or hedging.

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 read-only four-parameter calculator with fully documented schema and no output schema, the definition supplies enough for correct invocation: inputs must be a fixed plan and fixed fees, and the result is a maximum variable rate. The only gap is that no output schema exists and the description does not state the return shape or units beyond 'rate', which an agent must assume is EUR/kWh.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns slightly above that by framing the semantics: 'all-in variable rate' and 'fixed consumption budget' with fees implies budget minus fixed costs spread over planned kWh, which ties the four parameters into a single calculation. It still leaves the exact role of angebot_eur_kwh (a comparison benchmark, presumably) unstated.

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 ('bestimmen' / 'Compute') and a precise resource: the maximum all-in variable rate (Arbeitspreis) absorbable by a fixed consumption budget given fixed fees. That is far more specific than the bare tool name and tells an agent what result to expect. It stops short of differentiating itself from siblings such as strombudget_verbrauchsgrenze, which solves a related but inverse budget question.

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 phrase 'bei fest geplantem Verbrauch und Gebühren' implies the precondition for use (consumption and fees are already fixed), from which an agent can infer when this fits. However, there is no explicit when-to-use, no when-not-to-use, and no pointer to the sibling that answers the reverse question (how much consumption a rate allows). Usage is inferred rather than stated.

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