Skip to main content
Glama

getecoback-raumklima

stromfenster_mehrphasen_start

Read-only

Ein Gerät mit zwei unterschiedlich energieintensiven Phasen über bekannte Preisfenster einplanen — Find the cheapest contiguous start for a two-phase load.

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": {
      "preis_1_eur_kwh": "<preis_1_eur_kwh>",
      "preis_2_eur_kwh": "<preis_2_eur_kwh>",
      "preis_3_eur_kwh": "<preis_3_eur_kwh>",
      "preis_4_eur_kwh": "<preis_4_eur_kwh>",
      "phase_1_kwh": "<phase_1_kwh>",
      "phase_2_kwh": "<phase_2_kwh>"
    },
    "name": "stromfenster_mehrphasen_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
phase_1_kwhYesGemessene Energie in kWh während der ersten Gerätephase.
phase_2_kwhYesGemessene Energie in kWh während der zweiten Gerätephase.
preis_1_eur_kwhYesEndpreis im ersten gleich langen Zeitfenster, Euro pro kWh.
preis_2_eur_kwhYesEndpreis im zweiten gleich langen Zeitfenster, Euro pro kWh.
preis_3_eur_kwhYesEndpreis im dritten gleich langen Zeitfenster, Euro pro kWh.
preis_4_eur_kwhYesEndpreis im vierten gleich langen Zeitfenster, Euro pro 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 safety profile is covered and the description is consistent with it. The description adds that this is an optimization over contiguous windows, but it does not say what the result looks like (a start index, a time window, a cost) despite there being 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.

Conciseness3/5

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

It is short and front-loaded, but the same content is stated twice, once in German and once in English, which is redundant rather than reinforcing. The single useful clause about contiguous windows is buried in the second half.

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 six required numeric parameters, no output schema, and a non-obvious window-to-phase mapping, the description should say more about the result and the window semantics. The fully documented schema and the read-only annotations carry much of the burden, keeping this at a minimum-viable level.

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 the six numeric parameters are already documented, which sets the baseline at 3. The description adds no meaning beyond the schema and notably leaves the relationship between the four equal-length price windows and the two energy phases unexplained.

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 action and object: schedule a device with two phases of differing energy intensity across known price windows, i.e. find the cheapest contiguous start for a two-phase load. That is far more specific than the opaque tool name, though it never explains how the four price windows map onto the two phases, which is the core of the computation.

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 scenario is implied (a two-phase appliance plus known price windows), so an agent can infer when the tool applies. There is no explicit when-not guidance, no prerequisites, and no pointer to any alternative scheduling tool among the many siblings.

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