Skip to main content
Glama

getecoback-climate-weather

raumfeuchte_mittelwert_schwellenanteil

Read-only

Aus einem Bereich und Zeitmittel ableiten, welchen Schwellenanteil das Protokoll höchstens und mindestens zulässt — Bound time at or above a humidity threshold when only aggregate data survive.

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": {
      "zeitmittel_rh": "<zeitmittel_rh>",
      "unterste_moegliche_rh": "<unterste_moegliche_rh>",
      "oberste_moegliche_rh": "<oberste_moegliche_rh>",
      "schwelle_rh": "<schwelle_rh>"
    },
    "name": "raumfeuchte_mittelwert_schwellenanteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
schwelle_rhYesSelbst gewählte Prüfschwelle in % relativer Feuchte.
zeitmittel_rhYesBelegtes, zeitgewichtetes Mittel im vollständigen Fenster.
oberste_moegliche_rhYesBelegte Obergrenze der Feuchte im Fenster.
unterste_moegliche_rhYesBelegte Untergrenze der Feuchte im Fenster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 tool produces both an upper and lower bound rather than a point estimate, which is meaningful behavior beyond the annotations, but it does not say how tight those bounds are, what assumptions make them valid, or what happens if the supplied bounds are inconsistent with the mean.

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

Conciseness5/5

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

Two compact clauses: the German sentence front-loads the derivation and its outputs, and the English sentence adds the domain framing. No filler, and the key concept (bounding a threshold share) appears immediately.

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, four-required-parameter computation with no output schema, the definition explains what is derived but not the form of the result (fraction vs. percentage, one object with two fields, etc.). That is a real gap given there is no output schema to fall back on, though the core semantics are present.

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 humidity parameters are already documented with ranges and meanings. The description only loosely maps 'Bereich' to the min/max pair and 'Zeitmittel' to the mean, adding no units, ordering constraints, or validity conditions beyond the schema.

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 derivation ('ableiten, welchen Schwellenanteil ... höchstens und mindestens zulässt') from a defined input set (Bereich and Zeitmittel), and the English gloss clarifies that the result is time-at-or-above-threshold. It is not a restatement of the name, though the phrasing stays abstract enough that a reader must parse domain jargon to see the operation.

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?

The clause 'when only aggregate data survive' implicitly states the applicable situation (raw series unavailable, only min/max/mean retained), which is useful routing context. However, no sibling tool is named and no explicit when-not condition is given, so the agent must infer that the series-based sibling tools should be preferred when raw data exists.

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