Skip to main content
Glama

getecoback-climate-weather

dachfenster_haftstellen_wiederholungsprobe

Read-only

Vergleicht nur tatsächlich beobachtete Ablösungen nach einer gleich langen Nutzungsfolge — Compare observed roof-window seal detachments after equal sequences of use.

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": {
      "gepruefte_ecken": "<gepruefte_ecken>",
      "lose_frueher": "<lose_frueher>",
      "lose_spaeter": "<lose_spaeter>",
      "zyklus_gleich": "<zyklus_gleich>"
    },
    "name": "dachfenster_haftstellen_wiederholungsprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
lose_frueherYesBeim ersten Durchgang gelöste Eckstellen.
lose_spaeterYesBeim zweiten Durchgang gelöste Eckstellen.
zyklus_gleichYesGleiche Zahl regulärer Nutzungswechsel, Beobachtungsdauer und Eckstellen?
gepruefte_eckenYesZahl gleicher, von innen sichtbarer Eckstellen in beiden Durchgängen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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. Beyond that the description only adds the "observed only, no extrapolation" constraint; it does not say what happens when zyklus_gleich=false (error, refusal, or a flagged-but-computed result), which is the single most consequential behavior for calling this correctly.

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 with the scoping constraint placed first; nothing is padded. The German/English duplication costs a few words but usefully disambiguates a compound German tool name.

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, the description should say what the comparison yields. It leaves the return value entirely undefined and does not address how unequal or zero-valued inputs are handled, so an agent cannot predict the result.

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 all four parameters are already self-documenting with bounds and German labels. The description adds no format, unit, or relational semantics beyond what the schema carries, so the baseline of 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?

"Vergleicht ... Ablösungen" gives a specific verb and resource (detachment counts between two runs) and decodes the cryptic tool name. However, what is being compared — a rate, a difference, a pass/fail verdict — is never stated, and the phrase "nur tatsächlich beobachtete" is a scoping caveat rather than a purpose statement.

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 indication of when to pick this over sibling tools such as the other dachfenster_* checks, nor any stated prerequisite or exclusion. The implicit precondition "after an equal sequence of use" is buried and only partially rendered as a parameter, so an agent gets no routing guidance.

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