Skip to main content
Glama

getecoback-climate-weather

dachdurchwaermung_spitzenverzug_protokoll

Read-only

Die zeitliche Verzögerung zwischen einer gemessenen Dachoberflächen- und Raumspitze dokumentieren — Calculate the observed time lag between matched roof and indoor peaks.

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": {
      "dach_spitze_min": "<dach_spitze_min>",
      "raum_spitze_min": "<raum_spitze_min>",
      "intervall_min": "<intervall_min>",
      "ganze_spitzen_erfasst": "<ganze_spitzen_erfasst>"
    },
    "name": "dachdurchwaermung_spitzenverzug_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
intervall_minYesGrößte Messlücke in der betrachteten Reihe in Minuten.
dach_spitze_minYesZeitpunkt des höchsten erfassten Dachoberflächenwertes in Minuten seit Mitternacht.
raum_spitze_minYesZeitpunkt des höchsten erfassten Raumluftwertes an demselben Kalendertag.
ganze_spitzen_erfasstYesBeide Reihen erfassen Anstieg und anschließenden Rückgang am gleichen Tag ausreichend?

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 safety is covered. The description adds that this is a calculation over observed peaks, but leaves open behavioral questions an agent would care about: whether the lag is signed (indoor peak can precede roof peak), how midnight wraparound is handled, and what 'dokumentieren' means in a read-only tool — whether anything is persisted or only returned.

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?

Two short clauses with the operation front-loaded and no filler; the German/English duplication is mildly redundant but each half earns its place for a bilingual tool surface. Nothing is buried or padded.

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 4-required-parameter tool with no output schema, the description covers the input side adequately via the schema but says nothing about the return value (the lag's unit, sign, or validity flags). Given the simplicity of the computation this is acceptable, but an agent must guess at the result shape.

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 the four parameters are already well documented with units and ranges; the description only reinforces that the two peak values must be 'matched'. No additional semantics (e.g., how intervall_min or ganze_spitzen_erfasst affect the result) are supplied beyond the schema.

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 English half states a concrete operation ('Calculate the observed time lag') on a concrete pair of resources ('matched roof and indoor peaks'), which is far clearer than the opaque German compound name. It does not distinguish itself from the many sibling *_protokoll tools, but the verb+resource pairing is unambiguous on its own.

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?

The word 'matched' implies a precondition (the two peaks must belong to the same event/day), but the description never states when to use this versus other protocol tools or what to do when peaks are unmatched. Usage is inferable from the phrasing rather than spelled out.

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