Skip to main content
Glama

getecoback-raumklima

nachtluft_kuehlerer_aussenwert_vor_erstem_abfall

Read-only

Bestimme, ob ein gemessener Außen-Innen-Wechsel früh genug erfasst ist, um ihm eine spätere Nachtablesung gegenüberzustellen — Verify timing for an outdoor-to-indoor temperature crossover before a later reading

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": {
      "letzte_aussen_waermer_min": "<letzte_aussen_waermer_min>",
      "erste_aussen_kuehler_min": "<erste_aussen_kuehler_min>",
      "erste_innenreaktion_min": "<erste_innenreaktion_min>",
      "gleiches_zeitprotokoll": "<gleiches_zeitprotokoll>"
    },
    "name": "nachtluft_kuehlerer_aussenwert_vor_erstem_abfall"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleiches_zeitprotokollYesDieselbe örtliche Sensorposition und gemeinsame Uhr ohne Lücken um den Wechsel
erste_innenreaktion_minYesErste erfasste Innenablesung mit der gesuchten Veränderung
erste_aussen_kuehler_minYesErste darauf folgende Paarung mit kühlerer Außenluft
letzte_aussen_waermer_minYesLetzte zeitgleiche Messpaarung mit wärmerer Außenluft

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 and locality are covered and the description does not need to repeat them. What it adds beyond that is conceptual context (this is a timing-feasibility verdict, not a measurement), but it does not say what the verdict looks like, whether the answer is boolean, or what happens when the timing condition is not met. With no output schema, that leaves a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The intent is front-loaded, but the definition is a bilingual duplicate: the English half restates the German half almost verbatim, consuming roughly half the text without adding information. The sentence is also dense with compound jargon that could be unpacked more economically.

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?

All four required parameters are fully documented in the schema and annotations cover the read-only nature, so the definition is callable. It nevertheless leaves the agent guessing about the decision logic (what ordering or threshold makes the timing 'early enough') and about the shape of the returned verdict, which matters for a tool whose entire output is a judgement.

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%, with each of the four parameters carrying a precise German explanation including units (minutes, 0–10080 range) and the shared-protocol requirement. The description only supplies the overarching narrative of the crossover sequence and adds no per-parameter meaning beyond what the schema already states, so the baseline of 3 applies.

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 operation (verify whether a measured outdoor-to-indoor crossover is captured early enough to be compared against a later night reading), which is far more than a restatement of the cryptic German name. However, it does not differentiate itself from adjacent-sounding siblings such as the energy-comparison or note-substitution tools, so an agent must infer the boundary.

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 only implied through the phrase 'before a later reading' / 'um ihm eine spätere Nachtablesung gegenüberzustellen', which tells the agent this is a pre-condition check in a measurement sequence. There is no explicit when-not guidance, no stated prerequisites, and no named alternative for cases where the timing check fails.

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