Skip to main content
Glama

getecoback-climate-weather

betriebszustand_nachlauf_vor_messbeginn

Read-only

Ein bereits protokolliertes Messfenster auf Vermischung von Programmende, weiterem Nachlauf und stabilem Zustand prüfen — Exclude transitional minutes when a quiet-state sample began too early.

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": {
      "aufgabe_ende_min": "<aufgabe_ende_min>",
      "nachlauf_ende_min": "<nachlauf_ende_min>",
      "mess_start_min": "<mess_start_min>",
      "mess_ende_min": "<mess_ende_min>",
      "stabil_bis_ende": "<stabil_bis_ende>"
    },
    "name": "betriebszustand_nachlauf_vor_messbeginn"
  }
}

Input Schema

NameRequiredDescriptionDefault
mess_ende_minYesEnde desselben Messfensters.
mess_start_minYesBeginn des bereits aufgezeichneten Messfensters.
stabil_bis_endeYesDer einmal erreichte Zustand blieb ohne weitere Aktivität bis zum Messende belegt?
aufgabe_ende_minYesProtokolliertes Ende der Hauptaufgabe auf gemeinsamer Minutenachse.
nachlauf_ende_minYesBelegter frühester stabiler Beginn, nachdem auch der funktionale Nachlauf geendet hatte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 'prüfen' on an 'bereits protokolliertem' window is consistent with a non-mutating analysis. The description adds that the input is an existing recording, but says nothing about output shape, thresholds, or how the exclusion decision is reported, so credit beyond the annotations is limited.

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?

Two sentences, front-loaded with the check itself, but the second sentence is an English restatement of the German first sentence rather than added information. The mixed-language phrasing leaves 'Exclude transitional minutes' ambiguous — it reads as an imperative to the caller rather than a description of the tool's behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter computation with no output schema, so the description carries the burden of explaining what comes back and how the 'Vermischung' check is resolved. It provides neither the return semantics nor how conflicting minute values are handled, leaving a significant gap for an analysis tool.

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 coverage is 100%, so all five parameters are already documented, including their minute-axis semantics and the 0–10080 bounds. The description's mention of Programmende, Nachlauf and stabilem Zustand loosely echoes aufgabe_ende_min, nachlauf_ende_min and stabil_bis_ende but adds no new interpretation. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('prüfen') and an object ('ein bereits protokolliertes Messfenster'), plus the specific confusion it checks for: program end vs. further after-run vs. stable state. However, it never states what the tool actually produces (a verdict, a corrected window, a list of minutes), and nothing distinguishes it from the many sibling 'nachlauf' tools. Purpose is recognizable but not crisp enough for confident selection.

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 clause 'Exclude transitional minutes when a quiet-state sample began too early' implies the triggering situation, which is weak but real usage guidance. There is no explicit when-not guidance and no named alternative among the numerous after-run siblings the agent could pick instead.

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