Skip to main content
Glama

getecoback-climate-weather

strompreis_zwei_geraete_ruhefenster

Read-only

Zwei unterschiedlich energieintensive Läufe ohne zeitliche Überlagerung auf erlaubte Zeitfenster verteilen — Pick distinct low-cost slots for two planned chores that must not overlap.

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": {
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_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>",
      "a_nur_vor_fenster_3": "<a_nur_vor_fenster_3>",
      "b_nur_nach_fenster_1": "<b_nur_nach_fenster_1>"
    },
    "name": "strompreis_zwei_geraete_ruhefenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene kWh des vollständigen Laufs A.
b_kwhYesGemessene kWh des vollständigen Laufs B.
preis_1_eur_kwhYesBekannter Endpreis in Zeitfenster 1.
preis_2_eur_kwhYesBekannter Endpreis in Zeitfenster 2.
preis_3_eur_kwhYesBekannter Endpreis in Zeitfenster 3.
a_nur_vor_fenster_3YesLauf A muss vor dem dritten Zeitfenster beendet sein?
b_nur_nach_fenster_1YesLauf B darf frühestens im zweiten Zeitfenster beginnen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety and closed-world behavior are covered. The description adds the key non-overlap constraint and cost-minimization objective, but with no output schema it does not explain what the result looks like (assignment, feasibility, cost) or how infeasible cases are handled.

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 definition is short and front-loaded with the core scheduling objective. The bilingual repetition of the same sentence is slightly redundant but not enough to obscure the purpose.

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?

For a seven-parameter scheduling solver with no output schema, the description covers the main objective and non-overlap requirement but omits what the tool returns and how it behaves on infeasible inputs. It is adequate but not fully complete for the tool's complexity.

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%, and every parameter including the three price windows and two boolean scheduling constraints is documented in the schema. The description reinforces that the inputs are two energy-intensive runs and allowed windows, but adds no syntax or interpretation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('verteilen'/'Pick distinct low-cost slots') applied to a precise resource: two non-overlapping energy-intensive runs across allowed time windows. It clearly distinguishes the task from a single-device or overlapping schedule by naming the non-overlap constraint and the two planned chores.

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 implied by the scenario ('two planned chores that must not overlap') and the low-cost slot objective. However, it does not explicitly state when to prefer this tool over scheduling alternatives or when not to use it, leaving the agent to infer the selection context.

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