Skip to main content
Glama

getecoback-climate-weather

stromgruppe_gegenlaeufige_lastwechsel_netto

Read-only

Ein kaum verändertes Gruppenmittel trotz zweier entgegengesetzter Geräteänderungen anhand separater Messung einordnen — Identify real load cancellation hidden in the observed aggregate change.

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": {
      "gruppe_vor_w": "<gruppe_vor_w>",
      "gruppe_nach_w": "<gruppe_nach_w>",
      "a_zunahme_w": "<a_zunahme_w>",
      "b_abnahme_w": "<b_abnahme_w>",
      "kombifehler_w": "<kombifehler_w>",
      "zeitsynchron": "<zeitsynchron>"
    },
    "name": "stromgruppe_gegenlaeufige_lastwechsel_netto"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_zunahme_wYesSeparat gemessener Zuwachs von A zwischen den beiden Abschnitten.
b_abnahme_wYesSeparat gemessener Rückgang von B zwischen den beiden Abschnitten.
gruppe_vor_wYesGruppenmittel im ersten Messabschnitt.
zeitsynchronYesSind alle Werte aus denselben Zeitabschnitten und ohne Überschneidung der Gerätegrenzen?
gruppe_nach_wYesGruppenmittel im zweiten Abschnitt.
kombifehler_wYesBelegter kombinierter Fehlerrahmen der Änderungsschätzung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safe, closed-world, compute-only nature is covered structurally. The description adds the interpretive framing (that it separates genuine cancellation from an artifact of aggregation), but does not say what the assessment returns, how a false zeitsynchron value is handled, or how kombifehler_w influences the verdict. With no output schema, that is a real gap, though the annotations lower the bar.

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?

One front-loaded sentence plus an English restatement — the scenario comes first and the purpose second, with no filler. The bilingual duplication is mildly redundant since the English sentence adds no information beyond the German one, which keeps it from a 5.

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 six-parameter, all-required, computation-only tool with no output schema, the description establishes the scenario but not the result. An agent cannot tell from the definition whether it receives a boolean cancellation flag, a corrected net change, or an error/plausibility note, nor what happens when zeitsynchron is false. Reasonably complete on intent, incomplete on outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter carries its own German description with bounds, so the schema does the heavy lifting and the baseline of 3 is the floor. The description does add a little meaning by explaining the point of pairing a_zunahme_w with b_abnahme_w against the group before/after, which explains why these inputs are required together. It does not, however, explain how kombifehler_w or zeitsynchron affect the result.

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 scenario — an almost unchanged group mean despite two opposing device changes, measured separately — and frames the goal as identifying real load cancellation hidden in the aggregate. The verb 'einordnen' (classify/assess) is somewhat soft, but the resource and situation are specific enough that an agent knows this is a cancellation-detection tool rather than a generic aggregation tool. It does not name or distinguish itself from any sibling, which keeps it below a 5.

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 tightly described scenario: you use it when the group mean barely moved but two devices moved in opposite directions. There is no explicit when-not guidance, no statement of prerequisites beyond the required zeitsynchron flag, and no pointer to an alternative such as a direct sum tool. Adequate but leaves routing entirely to inference.

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