Skip to main content
Glama

getecoback-climate-weather

stromlast_zeitfenster_verschieben

Read-only

Kosten einer verschiebbaren Ladung für zwei bekannte Zeitfenster vergleichen. — Compare the gross running cost of a flexible load in two known tariff windows.

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": {
      "ladung_kwh": "<ladung_kwh>",
      "preis_jetzt": "<preis_jetzt>",
      "preis_spaeter": "<preis_spaeter>"
    },
    "name": "stromlast_zeitfenster_verschieben"
  }
}

Input Schema

NameRequiredDescriptionDefault
ladung_kwhYesEnergie für einen vollständigen Lauf in kWh.
preis_jetztYesBrutto-Arbeitspreis im ersten Zeitfenster in €/kWh.
preis_spaeterYesBrutto-Arbeitspreis im alternativen Zeitfenster in €/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, and the description is consistent with a pure comparison that mutates nothing and fetches nothing external. It adds the qualifier 'gross running cost', implying the prices are treated as brutto figures rather than net. It does not describe the returned comparison or how negative prices are handled, which the absent output schema leaves unexplained.

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?

The text is short and front-loaded with the purpose, so it is readable quickly. However, the German sentence and its English translation are near-duplicates, effectively spending two sentences on one idea without adding the missing usage or return 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?

For a three-parameter read-only calculation with full schema coverage and no output schema, the description covers purpose and the key interpretation nuance (brutto prices, two known windows). It is still thin on how the result should be read, for example whether a positive figure favors the later window.

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 three parameters are already documented with units and bounds. The description's only added meaning is 'gross' and 'flexible load', nudging the agent toward using brutto €/kWh values. Baseline 3 applies since the schema does the heavy lifting.

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 and resource: comparing running cost of a shiftable load across two known tariff windows. It also usefully corrects an impression the name 'zeitfenster_verschieben' might create, clarifying that nothing is shifted, only costs are compared. It does not differentiate itself explicitly from the many sibling energy-calculation tools.

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 rather than stated: an agent can infer this is for deciding between two known tariff windows, reinforced by 'zwei bekannte Zeitfenster'. There is no explicit when-not guidance, no mention of alternatives such as a full device-selection or consumption tool, and no prerequisite that prices must already be known.

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