Skip to main content
Glama

getecoback-raumklima

unterbrechbare_last_preisfenster_verteilen

Read-only

Benötigte Energie einer unterbrechbaren Aufgabe auf verfügbare Preisfenster verteilen — Allocate interruptible energy across known time slots with capacity limits.

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": {
      "bedarf_kwh": "<bedarf_kwh>",
      "preis_1_eur_kwh": "<preis_1_eur_kwh>",
      "preis_2_eur_kwh": "<preis_2_eur_kwh>",
      "preis_3_eur_kwh": "<preis_3_eur_kwh>",
      "verfuegbar_1_kwh": "<verfuegbar_1_kwh>",
      "verfuegbar_2_kwh": "<verfuegbar_2_kwh>",
      "verfuegbar_3_kwh": "<verfuegbar_3_kwh>"
    },
    "name": "unterbrechbare_last_preisfenster_verteilen"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedarf_kwhYesZielmenge in kWh.
preis_1_eur_kwhYesBekannter Endpreis für Fenster 1, Euro pro kWh.
preis_2_eur_kwhYesBekannter Endpreis für Fenster 2, Euro pro kWh.
preis_3_eur_kwhYesBekannter Endpreis für Fenster 3, Euro pro kWh.
verfuegbar_1_kwhYesIn Fenster 1 tatsächlich für diese Aufgabe verfügbare kWh.
verfuegbar_2_kwhYesIn Fenster 2 tatsächlich für diese Aufgabe verfügbare kWh.
verfuegbar_3_kwhYesIn Fenster 3 tatsächlich für diese Aufgabe verfügbare kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 side-effect-free, closed-world computation. The description usefully confirms the closed-world element by saying the windows are 'known' and bounded by 'capacity limits', but it says nothing about infeasibility (demand exceeding total capacity), tie-breaking between equal prices, or what the allocation result looks like; with no output schema that is a real disclosure gap.

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

Conciseness3/5

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

It is short and front-loaded, with the purpose in the first clause. However, the German sentence and the English sentence are near-verbatim translations of the same content, so half the text is redundancy rather than added information.

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 required inputs are fully self-documenting and the annotations cover the safety profile, so the essentials are present. Against that, this is a seven-parameter computation with no output schema and the description never indicates what is returned (per-window kWh allocation? cost?) or how an over-capacity demand is reported — the main things an agent cannot learn from the structured fields.

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% — every one of the seven required parameters (bedarf_kwh, preis_1..3_eur_kwh, verfuegbar_1..3_kwh) has its own unit-bearing description and bounds. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description names a specific verb (verteilen / allocate) and a specific resource (unterbrechbare Energie / interruptible energy) plus the target structure (known time slots with capacity limits). It is unambiguous what the tool computes, but it never contrasts itself with any sibling (e.g. the other *_verteilen tool), so the agent gets no differentiation signal.

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: the phrasing 'known time slots with capacity limits' and 'Benötigte Energie einer Aufgabe' suggests the situation (a fixed demand plus three known price windows with known available kWh). There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the applicability conditions.

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