Skip to main content
Glama

getecoback-climate-weather

hygrometer_minmax_ablesen_uebergabe

Read-only

Nach der Ableseübergabe klären, zu welchem Zeitraum ein Min-Max-Wert gehört — Identify whether a minimum or maximum can be assigned to the intended observation window.

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": {
      "fensterbeginn_min": "<fensterbeginn_min>",
      "ruecksetzung_min": "<ruecksetzung_min>",
      "ablesung_min": "<ablesung_min>",
      "ruecksetzung_bekannt": "<ruecksetzung_bekannt>"
    },
    "name": "hygrometer_minmax_ablesen_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
ablesung_minYesAblesung am selben Tag in Minuten seit Tagesbeginn.
ruecksetzung_minYesLetztes protokolliertes Zurücksetzen am selben Tag, bei unbekanntem Zeitpunkt 0.
fensterbeginn_minYesBeobachtungsbeginn in Minuten seit Tagesbeginn.
ruecksetzung_bekanntYesRücksetzung und Zeitpunkt wurden tatsächlich dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 the safety profile is covered and the bar is lower. The description adds that this is an attribution/validation step rather than a data fetch, but it never indicates what the call returns (a verdict, a window, an ambiguity flag) and does not say how the rücksetzung_bekannt=false branch is handled.

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?

Two short sentences, front-loaded with the trigger condition and then the task. The German/English duplication is mild redundancy but earns its place as a disambiguation aid in a domain-specific vocabulary; nothing else is wasted.

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 documented and annotations cover safety, so the calling contract is mostly complete. The notable gap is output: with no output schema, the agent has no idea whether to expect a boolean, an interval, or an ambiguity classification, which matters for a decision-style tool.

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 definition including the 0=unknown convention for ruecksetzung_min. The description adds no parameter-level meaning beyond that, 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?

States a concrete determination task: decide whether a min/max reading can be attributed to the intended observation window, with the bilingual gloss removing the main ambiguity. It is clear what the tool does, but it draws no boundary against adjacent siblings such as hygrometer_grenzuebertritt_zeitfenster or hygrometer_anzeige_vom_sitzplatz.

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 phrase 'Nach der Ableseübergabe' implies a procedural position — use this after the reading handover — which is real if thin guidance. No when-not conditions, prerequisites, or named alternatives are given, so the agent must infer the sequencing from the sibling context.

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