Skip to main content
Glama

getecoback-climate-weather

gefrierschrank_stoerstunden_herstellerwert_scope

Read-only

Ordne die Herstellerangabe zur Störlagerung einer belegten oder offenen Ausfalldauer zu — Scope the documented holdover figure against the recorded outage duration

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": {
      "genaues_modell": "<genaues_modell>",
      "aus_unten_h": "<aus_unten_h>",
      "aus_oben_h": "<aus_oben_h>",
      "dauergrenzen_belegt": "<dauergrenzen_belegt>"
    },
    "name": "gefrierschrank_stoerstunden_herstellerwert_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
aus_oben_hYesObere Grenze der belegten Dauer in Stunden
aus_unten_hYesUntere Grenze der belegten Dauer in Stunden
genaues_modellYesGenaue deutsche Modellkennung
dauergrenzen_belegtYesBeide beobachteten Zeitgrenzen gelten für diesen einen Ausfall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/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 carried by structured data, not the text. Beyond that the description adds almost nothing behavioral: it does not state what the scoped result looks like, how an "offene" duration (dauergrenzen_belegt=false) is treated, or what happens when the documented figure falls between the two bounds — a real 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.

Conciseness3/5

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

It is a single front-loaded clause, which is good, but the German and English halves are pure restatements of each other, so roughly half the text is redundant. The remainder is compact with no filler beyond that duplication.

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?

For a four-required-parameter comparison tool with no output schema and no annotations covering behavior, the description should say what the scoping outcome is and how the bounds are interpreted. Instead it restates the title-level concept in two languages and leaves the result semantics entirely undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented (model enum, upper/lower hour bounds, and the boolean flag) — baseline would be 3. The description adds no additional semantics for any parameter, and does not even convey the relationship between aus_unten_h/aus_oben_h or what the enum value "offen" implies for the computation.

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 names a specific action ("Ordne ... zu" / "Scope ... against") and two concrete operands: the manufacturer's documented holdover figure and the recorded outage duration. However, it never says what the tool actually produces from that comparison (a verdict, a margin, a classification), and it offers no differentiation from the many similarly named `*_scope` siblings in the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The phrase "belegten oder offenen Ausfalldauer" hints that two cases exist, but the agent is left to infer which case applies and when this tool is the right choice over e.g. `gefrierschrank_stromausfall_dauer_zwischen_ankern` or `gefrierschrank_zaehler_reset_downtime_energieluecke`.

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