Skip to main content
Glama

getecoback-climate-weather

stromlauf_mischplan_rueckrechnung_profilfehler

Read-only

Ein historisches Verbrauchsprofil gegen beobachtete Phasen nach Dauerfehler und Rate aufschlüsseln — Separate forecast discrepancies caused by mode duration from discrepancies within mode.

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": {
      "geplant_aktiv_stunden": "<geplant_aktiv_stunden>",
      "beobachtet_aktiv_stunden": "<beobachtet_aktiv_stunden>",
      "geplant_aktiv_wh_stunde": "<geplant_aktiv_wh_stunde>",
      "langsame_ruhe_wh_stunde": "<langsame_ruhe_wh_stunde>",
      "beobachtet_gesamt_wh": "<beobachtet_gesamt_wh>",
      "fenster_stunden": "<fenster_stunden>"
    },
    "name": "stromlauf_mischplan_rueckrechnung_profilfehler"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_stundenYesGesamtdauer des Plan- und Messfensters.
beobachtet_gesamt_whYesDurchgehend gemessene Wh des gesamten Fensters.
geplant_aktiv_stundenYesIn einer vergangenen Phase ursprünglich erwartete aktive Stunden.
geplant_aktiv_wh_stundeYesErwartete Wh je aktiver Stunde im alten Plan.
langsame_ruhe_wh_stundeYesIm alten Plan genutzte Wh je nicht aktiver Stunde.
beobachtet_aktiv_stundenYesBeobachtete aktive Stunden dieser Phase.

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. The description adds the conceptual decomposition behavior—duration-related versus within-mode discrepancy—but says nothing about return format, assumptions, or how the two components are reported, which is a notable gap given there is 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.

Conciseness4/5

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

It is a single bilingual purpose statement, front-loaded and free of procedural noise. The German and English sentences duplicate the same idea, which is mildly redundant but not harmful for an internationalized tool.

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 read-only calculation tool with no output schema, the description explains the analytical intent but not what the result looks like or how to interpret the separated discrepancy components. The parameters themselves are fully documented, so this is adequate but incomplete at the output boundary.

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?

All six parameters are required and have 100% schema description coverage, including units and bounds. The description does not mention parameter names or add syntax beyond the schema, so the baseline of 3 applies.

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 English clause names a specific analytical operation: separating forecast discrepancies caused by mode duration from discrepancies within mode. The German clause adds that the input is a historical consumption profile compared against observed phases. It is clear enough, though the cryptic tool name and lack of explicit sibling differentiation keep it from 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?

The description implies the tool is for diagnosing forecast error in time-of-use or active-mode energy analysis, but it never states when to choose this over other diagnostic tools, nor any prerequisites or exclusions. This is implied usage rather than explicit guidance.

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