Skip to main content
Glama

getecoback-raumklima

feuchtequelle_abfolge_vor_lueftungsprobe

Read-only

Bestimme, ob eine Feuchtemessung den Fensterwechsel von einer vorherigen Feuchtequelle zeitlich trennt — Check whether a ventilation observation excludes the preceding moisture event

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": {
      "quelle_ende_min": "<quelle_ende_min>",
      "fenster_auf_min": "<fenster_auf_min>",
      "vergleich_alt_min": "<vergleich_alt_min>",
      "ausgleich_min": "<ausgleich_min>"
    },
    "name": "feuchtequelle_abfolge_vor_lueftungsprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausgleich_minYesEigenes vorab gewähltes Mindestintervall nach Ende der Quelle
fenster_auf_minYesZeitpunkt des Öffnens in derselben Zeitskala
quelle_ende_minYesDokumentiertes Ende der Feuchtequelle
vergleich_alt_minYesZeitpunkt der als Ausgangspunkt geplanten Innenablesung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: it does not say whether the result is a boolean, how the custom minimum interval (ausgleich_min) is compared, or what happens at boundary/negative intervals.

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?

It is short and the verb is front-loaded, but the German and English halves are near-duplicates whose wording does not match exactly, adding ambiguity rather than precision. The single sentence carries no structure to distinguish inputs from the decision rule.

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

Completeness2/5

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

For a four-parameter deterministic check with no output schema, the description should state the comparison rule and the shape of the answer. Instead it only gestures at the intent, leaving an agent unable to predict what 'true' would mean or how the custom interval is applied.

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 four required temporal parameters are already documented in the schema. The description does not clarify how quelle_ende_min, fenster_auf_min, vergleich_alt_min and ausgleich_min combine into the decision, so it stays at the baseline.

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 states a specific verb and target of judgement ('Bestimme, ob ... zeitlich trennt' / 'Check whether ... excludes'), so an agent knows this is a predicate check rather than a data-fetch. It is weakened by the two framings diverging (a moisture measurement separating a window change vs. a ventilation observation excluding an event) and by no differentiation from the many sibling checks.

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 or when-not guidance and no named alternative among the many sibling predicate tools. The only cue is the implicit 'vor Lueftungsprobe' in the name, which the description itself never restates.

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