Skip to main content
Glama

getecoback-climate-weather

stromgruppe_anlaufstaffel_kosten_und_messspitze

Read-only

Zwei bereits erprobte Startfolgen nach Energie und gemessenem Maximum unabhängig vergleichen — Check whether a staggered start lowered the observed peak while using more energy.

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": {
      "gleichzeitig_wh": "<gleichzeitig_wh>",
      "gestaffelt_wh": "<gestaffelt_wh>",
      "gleichzeitig_max_w": "<gleichzeitig_max_w>",
      "gestaffelt_max_w": "<gestaffelt_max_w>",
      "aufgabe_und_raster_gleich": "<aufgabe_und_raster_gleich>"
    },
    "name": "stromgruppe_anlaufstaffel_kosten_und_messspitze"
  }
}

Input Schema

NameRequiredDescriptionDefault
gestaffelt_whYesEnergie des vollständigen Versuchs mit gestaffelten Starts.
gleichzeitig_whYesEnergie des vollständigen Versuchs mit gemeinsamem Start.
gestaffelt_max_wYesHöchste Intervallmittel-Leistung bei gestaffelten Starts.
gleichzeitig_max_wYesHöchste Intervallmittel-Leistung bei gemeinsamem Start.
aufgabe_und_raster_gleichYesSind Aufgabenergebnis, Messgrenze und Auflösung vergleichbar?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds the analytical framing (did staggering lower the peak at the cost of more energy), but says nothing about what the comparison returns, and there is no output schema to fall back on.

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-loads the comparison before the interpretive question. The bilingual restatement of the same idea is mildly redundant but serves as clarification rather than noise.

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 five-required-parameter tool with no output schema, the description covers the input side adequately but leaves the return value unexplained, and it never mentions the comparability precondition captured by aufgabe_und_raster_gleich. It is workable but not complete.

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 five parameters are documented in the schema itself. The description adds only the framing that both value pairs come from completed trials; it does not explain the comparability gate parameter or how mismatched trials are handled.

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 (compare two already-tested start sequences) and the two comparison axes (energy and measured peak), which lets an agent distinguish this from the many sibling tools about measurement completeness or tariffs. It stops short of naming a sibling it is not, so it does not reach the top score.

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?

"Zwei bereits erprobte Startfolgen" implies a prerequisite: both runs must already be measured before calling this. There is no explicit when-not guidance and no alternative tool is named, so the usage context is suggested rather than stated.

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