Skip to main content
Glama

getecoback-climate-weather

klimafenster_rueckbau_ereignisse_zeitfolge

Read-only

Prüft Zeitstempel eines abgeschlossenen Rückbaus auf dokumentierte Reihenfolge — Check the recorded sequence of shutdown, kit removal and window closure.

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": {
      "aus_min": "<aus_min>",
      "abnahme_fertig_min": "<abnahme_fertig_min>",
      "geschlossen_min": "<geschlossen_min>",
      "gleicher_zeitbezug": "<gleicher_zeitbezug>"
    },
    "name": "klimafenster_rueckbau_ereignisse_zeitfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
aus_minYesBeobachtetes reguläres Abschalten ab Beginn des Protokolls in Minuten.
geschlossen_minYesDokumentierter Fensterschluss in Minuten.
abnahme_fertig_minYesBeobachtete vollständige Abnahme in Minuten.
gleicher_zeitbezugYesStammen alle drei Werte aus demselben Protokoll mit gemeinsamem Zeitnullpunkt?

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 establish that this is a safe read-only, closed-world operation, so the description does not need to restate safety. It adds that the check concerns documented ordering of shutdown, kit removal, and window closure, but it does not explain the expected order or what the result indicates.

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 short and front-loaded, moving directly from the German check statement to the English clarification. The bilingual duplication is slightly redundant but does not obscure the core action.

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?

For a read-only validation tool with fully documented parameters and annotations, the description covers the basic check. However, it leaves important behavioral context implicit: the expected temporal order, what happens when the order is wrong, and what the tool returns, with no output schema to compensate.

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?

All four parameters are fully described in the schema, including ranges and the shared-time-reference boolean. The description adds conceptual context about the sequence being validated but does not provide any additional parameter-level meaning beyond what the schema already states.

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 verification action: checking timestamps of a completed dismantling for documented sequence. It names the sequence elements (shutdown, kit removal, window closure), so the core purpose is clear, though it does not explicitly distinguish itself from similarly named sibling tools.

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 implied by 'eines abgeschlossenen Rückbaus' — the tool applies after dismantling is complete and when recorded ordering must be checked. It gives no explicit when-not guidance or alternative-tool routing, so it remains only partially guided.

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