Skip to main content
Glama

getecoback-climate-weather

gefrierschrank_stromausfall_dauer_zwischen_ankern

Read-only

Grenze die Länge einer belegten Unterbrechung aus vier verlässlichen Strombeobachtungen ein — Bound the outage duration from four verified power 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": {
      "letzter_strom_min": "<letzter_strom_min>",
      "erstmals_aus_min": "<erstmals_aus_min>",
      "zuletzt_aus_min": "<zuletzt_aus_min>",
      "erstmals_wieder_strom_min": "<erstmals_wieder_strom_min>",
      "ein_ausfall_und_uhr_bestaetigt": "<ein_ausfall_und_uhr_bestaetigt>"
    },
    "name": "gefrierschrank_stromausfall_dauer_zwischen_ankern"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuletzt_aus_minYesLetzte Beobachtung ohne Versorgung
erstmals_aus_minYesErste Beobachtung ohne Versorgung
letzter_strom_minYesLetzte Beobachtung mit Versorgung vor dem Ausfall
erstmals_wieder_strom_minYesErste Beobachtung mit Versorgung nach dem Ausfall
ein_ausfall_und_uhr_bestaetigtYesEindeutig dieselbe zusammenhängende Unterbrechung, alle Zeiten auf einer Referenz

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 that the result is a bound rather than an exact duration and that the four observations must belong to one contiguous, clock-consistent outage — useful context, but nothing about permissions, edge-case behavior (e.g. equal timestamps) or the returned interval.

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?

A single front-loaded sentence stating the operation and its inputs, with a parallel English rendering for accessibility. It is efficient, though the bilingual duplication adds length without adding information.

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?

With five required parameters, no output schema and no annotations about return values, the definition should say what the tool produces (an interval with lower and upper bounds, units, ordering). 'Grenze ... ein' hints at bounds but the response shape is never described, leaving a real gap for a pure computation 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 description coverage is 100%, so every parameter already carries its own German explanation and 0–10080 minute range. The description only restates that four of the five inputs are observations, adding no interpretation beyond the schema; baseline 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 description names a specific operation (einen Bereich eingrenzen / bound an interval) on a specific quantity (Länge einer belegten Unterbrechung) and states the method (aus vier verlässlichen Strombeobachtungen). An agent can distinguish this from siblings like stromausfall_nachlauf_und_ruhe or gefrierschrank_versorgungsrueckkehr_anzeige_separat by the four-observation bounding approach, though no sibling is named explicitly.

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: call this when four verified power observations bracket a single outage. There is no explicit when-to-use versus when-not-to-use guidance and no pointer to an alternative tool for cases with fewer observations or an unconfirmed single outage, leaving the agent to infer the preconditions.

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