Skip to main content
Glama

getecoback-climate-weather

gefrierschrank_versorgungsrueckkehr_anzeige_separat

Read-only

Prüfe, ob die beobachtete Geräteanzeige nach belegter Stromrückkehr überhaupt zeitlich zugeordnet werden kann — Separate power restoration from display restart evidence

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": {
      "versorgung_min": "<versorgung_min>",
      "display_min": "<display_min>",
      "kontrollfenster_min": "<kontrollfenster_min>",
      "display_und_versorgung_gleicher_bezug": "<display_und_versorgung_gleicher_bezug>"
    },
    "name": "gefrierschrank_versorgungsrueckkehr_anzeige_separat"
  }
}

Input Schema

NameRequiredDescriptionDefault
display_minYesZeitpunkt der ersten belegten Anzeige am genau identifizierten Gerät
versorgung_minYesErste unabhängige bestätigte Versorgung auf gemeinsamer Zeitbasis
kontrollfenster_minYesSelbst festgelegte Dauer der geplanten Nachkontrolle ab bestätigter Versorgung
display_und_versorgung_gleicher_bezugYesZeitmarken betreffen das passende Gerät und den richtigen Versorgungsumfang

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 conceptual rule being applied (temporal attributability of display evidence), but says nothing about what the outcome looks like or how a negative verdict should be interpreted, which matters since no output schema exists.

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?

Two compact clauses, German statement front-loaded followed by an English restatement that earns its place by disambiguating the terminology. No filler, though the bilingual duplication is mildly redundant.

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?

All four parameters are required and fully documented in the schema, and the tool is read-only. However, with no output schema, an agent still cannot tell whether the result is a boolean verdict, a margin, or a textual explanation, and the description does not cover that gap.

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 parameter (versorgung_min, display_min, kontrollfenster_min, display_und_versorgung_gleicher_bezug) carries its own explanation with bounds, so the schema does the heavy lifting. The description adds no additional meaning such as ordering constraints between the two time markers or how the control window is used in the decision.

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 check ('Prüfe, ob ...') on a specific subject: whether the observed device display can be temporally attributed after a confirmed power restoration, and the English gloss clarifies the intent as separating power-restoration from display-restart evidence. It is clear enough to distinguish from generic freezer evidence tools, though it never names a sibling that would be the alternative.

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 only implied: the check belongs before crediting a display timestamp as evidence of restoration. There is no explicit when-to-use/when-not statement, no prerequisite described, and no alternative tool named for the case where the display is already unambiguously attributable.

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