Skip to main content
Glama

getecoback-climate-weather

sommerlueftung_tiefpunkte_zur_offenphase

Read-only

Ordnet gemessene Innen- und Außentiefpunkte der protokollierten Fensteröffnung zu — Locate observed indoor and outdoor minimum temperatures relative to window opening.

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": {
      "aussen_tief_min": "<aussen_tief_min>",
      "innen_tief_min": "<innen_tief_min>",
      "offen_ab_min": "<offen_ab_min>",
      "geschlossen_ab_min": "<geschlossen_ab_min>",
      "gleicher_zeitbezug": "<gleicher_zeitbezug>"
    },
    "name": "sommerlueftung_tiefpunkte_zur_offenphase"
  }
}

Input Schema

NameRequiredDescriptionDefault
offen_ab_minYesProtokollierte Öffnung ab demselben Start in Minuten.
innen_tief_minYesMinute des niedrigsten beobachteten Innenwerts ab demselben Start in Minuten.
aussen_tief_minYesMinute des niedrigsten beobachteten Außenwerts ab Start in Minuten.
geschlossen_ab_minYesProtokollierter Fensterschluss in Minuten.
gleicher_zeitbezugYesGleiche Uhrzeitbasis, vergleichbare Abtastrate und dasselbe Beobachtungsfenster?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description does not contradict it. The description adds the comparison intent, but says nothing about what the assignment produces (a classification? a verdict on whether the minimum fell inside the opening?) or what happens if 'gleicher_zeitbezug' is false. With annotations carrying safety, a 3 fits.

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 stating the operation, followed by an English restatement. It is efficient, though the bilingual duplication adds length without adding information for an English-only reader.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small, fully-specified, read-only computation tool with 100% schema coverage and no output schema, the description supplies everything needed to decide and call correctly: the operands and the relationship being evaluated. Remaining unknowns (return shape) are minor for a pure calculation.

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 five parameters, including the minute bounds and the 'gleicher_zeitbezug' precondition, are already documented in the schema. The description only restates the concepts (indoor minimum, outdoor minimum, opening) without adding format, ordering, or interpretation guidance. Baseline 3 applies when the schema does the heavy lifting.

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+resource pair: it assigns ('ordnet zu') observed indoor and outdoor minimum-temperature timestamps to the logged window-opening phase. An agent can understand the computation from the text alone. It does not, however, contrast itself with neighboring sommerlueftung tools such as stossfolgen_zwischenwaerme, so sibling differentiation is absent.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The intended context (relating measured minima to an opening interval) is only inferable from the operation described, not stated as a routing rule.

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