Skip to main content
Glama

getecoback-climate-weather

dachfenster_kit_abnahme_zeitstreuung

Read-only

Ermittelt die beobachtete Dauerstreuung bis ein Dachfenster nach Kitabnahme geschlossen war — Find the observed range of normal closure times after kit removal.

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": {
      "erster_min": "<erster_min>",
      "zweiter_min": "<zweiter_min>",
      "dritter_min": "<dritter_min>",
      "vorlauf_min": "<vorlauf_min>"
    },
    "name": "dachfenster_kit_abnahme_zeitstreuung"
  }
}

Input Schema

NameRequiredDescriptionDefault
erster_minYesZeit vom regulären Abschalten bis zum dokumentierten Fensterschluss im ersten Versuch in Minuten.
dritter_minYesZeit im dritten gleichartigen Versuch in Minuten.
vorlauf_minYesVerfügbare Zeit vor einem bereits feststehenden Termin in Minuten.
zweiter_minYesZeit im zweiten gleichartigen Versuch in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 covered structurally. Beyond that the description adds nothing: it does not say whether this is a pure local computation, how the three trial values and the deadline value interact, what happens if vorlauf_min is smaller than a measured duration, or what form the resulting range takes.

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 definition is a single front-loaded sentence that states the measured quantity immediately, with no filler. The bilingual German/English duplication is mild redundancy but does not obscure meaning.

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 four-required-parameter computation with no output schema, so the description is the only place to explain what comes back. It never says whether the result is a min/max interval, a tolerance verdict, or how vorlauf_min (a deadline constraint) changes the outcome, leaving an agent unable to predict the return value.

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 four minute-valued parameters carries its own German explanation, so the schema does the heavy lifting. The description adds no interpretation beyond restating the concept, which is the expected baseline of 3 when the schema is fully documented.

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 verb (Ermittelt/Find) and a specific computed quantity (the observed range/spread of normal closure duration after kit removal), which is precise enough for an agent to understand what the tool returns. It does not, however, distinguish the tool from the many closely named dachfenster_* siblings that also concern kit removal and window state, so the agent must guess its niche.

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 statement of which situation calls for a Streuungsberechnung versus the neighboring kit-abnahme or schliessprobe tools, and no prerequisites or exclusions. The agent must infer usage entirely from the name.

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