Skip to main content
Glama

getecoback-raumklima

kuehlprobe_innen_und_aussen_zeitgewichtete_luecke

Read-only

Trenne den mittleren gemessenen Temperaturabstand von einer offenen Messphase ohne Paarung — Report observed paired temperature gaps and their uncovered time

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": {
      "a_innen_c": "<a_innen_c>",
      "a_aussen_c": "<a_aussen_c>",
      "a_min": "<a_min>",
      "b_innen_c": "<b_innen_c>",
      "b_aussen_c": "<b_aussen_c>",
      "b_min": "<b_min>",
      "gesamt_min": "<gesamt_min>",
      "paare_disjunkt": "<paare_disjunkt>"
    },
    "name": "kuehlprobe_innen_und_aussen_zeitgewichtete_luecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_minYesDauer des belegten Abschnitts A
b_minYesDauer des weiteren belegten Abschnitts B
a_innen_cYesInnenabschnitt A, zeitlicher Mittelwert
b_innen_cYesGemittelter Innenwert B
a_aussen_cYesZeitlich passend gemittelter Außenwert A
b_aussen_cYesZeitlich passend gemittelter Außenwert B
gesamt_minYesGesamte betrachtete Dauer einschließlich Datenlücke
paare_disjunktYesZwei getrennte Messabschnitte und vergleichbare Messorte bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 the operation distinguishes paired gaps from an uncovered/open phase and reports both, which is genuine behavioral context. It does not, however, state the key invariant that the two segments must be disjoint or how gesamt_min relates to the reported uncovered time.

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 definition is short but wastes space on a near-duplicate English restatement of the German clause rather than front-loading what the tool returns. Content is not padded, but the redundant bilingual echo reduces efficiency.

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 computation tool with a fully documented 8-parameter schema and annotations, most call correctness is supported by structured fields. Still, with no output schema, the description should more precisely characterize the return (paired gaps and uncovered duration), which it only gestures at.

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 all 8 parameters documented (a_min, b_min, gesamt_min, temperature means, paare_disjunkt), so the schema carries parameter meaning. The description's 'offene Messphase' and 'uncovered time' loosely tie to gesamt_min and the gap concept but add no syntax or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Trenne' (separate) and the resources 'Temperaturabstand' vs 'offene Messphase ohne Paarung' give a rough sense that this is a compute/report tool comparing paired temperature gaps against uncovered time. However, the phrasing is dense and bilingual-redundant, and it never states plainly what the returned quantity is (a gap in °C versus a duration in minutes), so an agent must infer the exact purpose.

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 when-to-use guidance and no exclusions. The many sibling 'luecke'/'kuehlprobe' tools mean routing matters, yet the description never says when this tool applies versus e.g. klimafenster_kuehlprobe_zwei_nutzungsorte. The implied precondition (two disjoint paired segments) is only encoded in a schema parameter, not stated as a usage 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