Skip to main content
Glama

getecoback-climate-weather

dachraum_wiedererholung_gegen_aussen

Read-only

Nach Ende einer Hitzespitze prüfen, ob der Innen-Außen-Abstand trotz fallender Außenwerte wächst — Flag a delayed indoor rebound after outdoor conditions ease.

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": {
      "innen_start_c": "<innen_start_c>",
      "aussen_start_c": "<aussen_start_c>",
      "innen_ende_c": "<innen_ende_c>",
      "aussen_ende_c": "<aussen_ende_c>",
      "gleiche_messorte": "<gleiche_messorte>"
    },
    "name": "dachraum_wiedererholung_gegen_aussen"
  }
}

Input Schema

NameRequiredDescriptionDefault
innen_ende_cYesRaumwert bei der späteren gleichzeitigen Messung.
aussen_ende_cYesAußenwert bei derselben späteren Messung.
innen_start_cYesRaumwert bei der ersten gleichzeitigen Messung.
aussen_start_cYesAußenwert bei derselben ersten Messung.
gleiche_messorteYesUnveränderte Messorte, Außensensor verschattet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true and openWorldHint=false already declare a pure, closed-domain computation, so the description need not restate safety. It adds the interpretive framing (delayed rebound, easing outdoor conditions) but says nothing about what the evaluation produces — a flag, a boolean, a margin — which matters because there is no output schema.

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?

One compact sentence plus a translated restatement — no padding, and the trigger condition comes first. The German/English duplication is slightly redundant but aids disambiguation, so it does not seriously hurt.

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?

A five-parameter, all-required computation with no output schema needs the description to say what comes back and how the flag is derived from the four temperatures. The definition frames the question well but stops before the result, leaving a real gap for an agent deciding whether to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description earns one extra point by explaining the comparison logic: "trotz fallender Außenwerte" tells the agent that the start/end outdoor pair is expected to decrease while the gap grows, which is more than the per-field schema text conveys on its own.

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 diagnostic check: whether the indoor-outdoor temperature gap widens despite falling outdoor values after a heat spike, with an explicit English gloss ("delayed indoor rebound"). That is a concrete verb+resource, but it does not distinguish itself from neighbouring diagnostic siblings such as bad_feuchte_erholung_protokoll.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger condition is explicit and front-loaded: "Nach Ende einer Hitzespitze". An agent knows when the tool applies. No exclusions or named alternative tools are given, which keeps it short of a 5.

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