Skip to main content
Glama

getecoback-raumklima

strombudget_optionale_zyklen_priorisieren

Read-only

Zwei Arten geplanter Zusatzläufe nach eigener Priorität unter einem verbleibenden Strombudget einteilen — Allocate full optional runs in priority order after essential use and reserve.

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_kwh": "<budget_kwh>",
      "grundbedarf_kwh": "<grundbedarf_kwh>",
      "reserve_kwh": "<reserve_kwh>",
      "wichtige_zyklen": "<wichtige_zyklen>",
      "wichtiger_zyklus_kwh": "<wichtiger_zyklus_kwh>",
      "weitere_zyklen": "<weitere_zyklen>",
      "weiterer_zyklus_kwh": "<weiterer_zyklus_kwh>"
    },
    "name": "strombudget_optionale_zyklen_priorisieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_kwhYesGesamtgrenze des gewählten Zeitraums in kWh.
reserve_kwhYesVorab freizuhaltende Reserve in kWh.
weitere_zyklenYesGewünschte Anzahl der weniger wichtigen optionalen Läufe.
grundbedarf_kwhYesBereits eingeplanter unverzichtbarer Bedarf in kWh.
wichtige_zyklenYesGewünschte Anzahl der wichtigeren optionalen Läufe.
weiterer_zyklus_kwhYesGemessene kWh pro weiterem Lauf.
wichtiger_zyklus_kwhYesGemessene kWh pro wichtigem Lauf.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds allocation order and reserve handling, but it does not explain the result shape or what happens when the remaining budget is insufficient for all requested runs.

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?

The main sentence is front-loaded and efficient, and the priority condition is clear. The English restatement after the em dash duplicates the German without adding new behavioral detail, so it is slightly less tight than it could be.

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?

With seven required numeric inputs and no output schema, the description should do more to explain the returned allocation or edge-case handling. It conveys the core logic but leaves an agent unable to predict the exact result structure or tie/insufficiency behavior.

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 seven parameters are already documented in the schema. The description reinforces the concepts of essential demand, reserve, and two priority classes, but it adds no parameter-level meaning beyond the schema baseline.

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 specific verb ('einteilen') and resource ('Zwei Arten geplanter Zusatzläufe') and frames them under a remaining electricity budget after essential use and reserve. It is clear what the tool does, though it does not explicitly distinguish itself from the strombudget_* siblings.

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?

It gives the key usage condition: allocation happens after essential use and reserve, and in priority order. However, it does not name alternatives, state when not to use this tool, or explain how to choose among related strombudget_* tools.

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