Skip to main content
Glama

getecoback-raumklima

stromverlauf_planband_vs_messband

Read-only

Eine vorab dokumentierte Verbrauchsspanne mit dem späteren Messintervall statt nur mit dessen Mittelwert beurteilen — Backtest a projected range against independently bounded observations.

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": {
      "plan_min_kwh": "<plan_min_kwh>",
      "plan_max_kwh": "<plan_max_kwh>",
      "mess_min_kwh": "<mess_min_kwh>",
      "mess_max_kwh": "<mess_max_kwh>",
      "gleiches_fenster": "<gleiches_fenster>"
    },
    "name": "stromverlauf_planband_vs_messband"
  }
}

Input Schema

NameRequiredDescriptionDefault
mess_max_kwhYesNachträglich begründete obere Grenze des gemessenen Verbrauchs.
mess_min_kwhYesNachträglich begründete untere Grenze des gemessenen Verbrauchs.
plan_max_kwhYesVorab dokumentierte obere Annahme für dasselbe Fenster.
plan_min_kwhYesVorab dokumentierte untere Annahme für den späteren Gesamtverbrauch.
gleiches_fensterYesZeit, Zählerumfang und Verbrauchsaufgabe stimmen zwischen Plan und Messung überein?

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 methodological context by emphasizing interval bounds instead of a mean, but it does not explain the comparison logic, output form, or edge cases such as non-overlapping or reversed bounds. This is useful but limited behavioral context beyond annotations.

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 description is two compact clauses separated by an em dash and is front-loaded with the core comparison. It contains no filler or repetition of the tool name. The bilingual phrasing is slightly less clean but remains efficient.

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-parameter analytical tool with no output schema, the description should clarify what result the backtest produces, such as whether the measurement interval lies within the plan band or how discrepancies are reported. It explains the comparison concept but not the return value or interpretation. The schema fully covers inputs, but output behavior remains unspecified.

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 each of the five parameters already has a precise German description including bounds and meaning. The tool description does not add syntax, format, or validation details beyond what the schema provides. Baseline 3 is appropriate because the schema carries parameter semantics.

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 analytical action: assessing a pre-documented consumption range against a later measurement interval rather than only its mean. The English phrase 'Backtest a projected range against independently bounded observations' reinforces the purpose. It does not name or differentiate from any sibling tool, so it falls short of 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 presence of both a plan range and a measurement range, and the description contrasts interval comparison with mean-only comparison. However, it gives no explicit when-to-use conditions, prerequisites, or when-not guidance. An agent can infer the context but is not routed to alternatives.

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