Skip to main content
Glama

getecoback-climate-weather

raumfeuchte_intervall_hoch_bleibt_nach_quellenende

Read-only

Trenne hohe Feuchte während einer Quelle von belegten Minuten nach ihrem Ende — Separate high humidity during an event from its documented persistence afterwards

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": {
      "hoch_ab_min": "<hoch_ab_min>",
      "hoch_bis_min": "<hoch_bis_min>",
      "quelle_bis_min": "<quelle_bis_min>",
      "gleicher_sensor_durchgehend": "<gleicher_sensor_durchgehend>"
    },
    "name": "raumfeuchte_intervall_hoch_bleibt_nach_quellenende"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoch_ab_minYesNach eigener Protokollregel belegter Beginn der erhöhten Feuchte
hoch_bis_minYesBelegtes Ende oder letzter durchgehend erfasster Zeitpunkt
quelle_bis_minYesEnde der bekannten Feuchtequelle in derselben Zeitskala
gleicher_sensor_durchgehendYesKein Messortwechsel und kein Aufzeichnungsausfall im angegebenen Abschnitt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 safety is covered. The description adds no behavioral context beyond the bare framing: it does not say what happens when 'gleicher_sensor_durchgehend' is false, whether intervals must be ordered or non-overlapping, or what the result represents, which matters for a computation whose inputs are all required and constrained to a 10080-minute window.

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 in German with an English mirror, with no filler or repetition. The bilingual duplication costs a little space but aids disambiguation.

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?

There is no output schema and the description never indicates what a 'separation' returns (two durations, a split interval list, a boolean classification). For a four-required-parameter computation tool with no output schema, this leaves a significant gap an agent cannot resolve from structured fields.

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 each of the four parameters is already documented in the schema. The description contributes only the framing that hoch_* marks the event interval while quelle_bis_min marks the source's end, which reinforces but does not extend the schema semantics.

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 description gives a specific verb ('Trenne'/'Separate') and a domain resource (high humidity during an event vs. its persistence afterwards), so the operation is identifiable. However, the phrasing is abstract and does not state what the separation produces or how it relates to the raumfeuchte_* siblings, leaving the exact output shape unclear.

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 guidance, no exclusion conditions, and no reference to alternatives such as raumfeuchte_abschnitte_zeitgewichtet or raumfeuchte_mittelwert_schwellenanteil. The use case must be inferred entirely from the phrase 'during an event ... from its documented persistence afterwards'.

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