Skip to main content
Glama

getecoback-climate-weather

keller_hygrometer_anzeige_obere_messgrenze

Read-only

Hohen Kellerfeuchtewert an der spezifizierten Anzeigegrenze als begrenzte Beobachtung kennzeichnen — Distinguish a capped humidity reading from a usable measurement.

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": {
      "angezeigte_rf": "<angezeigte_rf>",
      "obergrenze_rf": "<obergrenze_rf>",
      "grenze_bestaetigt": "<grenze_bestaetigt>",
      "kondensat_am_fuehler": "<kondensat_am_fuehler>"
    },
    "name": "keller_hygrometer_anzeige_obere_messgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
angezeigte_rfYesAngezeigte relative Feuchte in Prozent.
obergrenze_rfYesObere für diese Bedingungen dokumentierte Anzeige- oder Messgrenze.
grenze_bestaetigtYesGrenze aus dem Handbuch des genauen Hygrometers übernommen?
kondensat_am_fuehlerYesWar Feuchte auf dem Sensor sichtbar oder wird in der Anleitung eine Kondensation ausgeschlossen?

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?

readOnlyHint=true and openWorldHint=false already establish that this is a safe, closed-world read, so the description's added value is the semantic framing of a capped observation. It does not say what the marking produces, whether an unconfirmed limit changes the outcome, or how condensation at the sensor affects the classification.

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 with no filler; the German/English duplication is mildly redundant but each version carries the same precise distinction, and nothing is buried.

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?

With four required parameters, no output schema, and only two annotations, the description should clarify how grenze_bestaetigt and kondensat_am_fuehler influence the verdict and what the flagging yields. It conveys the purpose but leaves the decision logic and result shape unstated.

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% and each parameter already carries a German description plus bounds, so the schema does the heavy lifting. The description mentions no parameter at all, adding no meaning beyond the schema — baseline 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?

The description names a concrete operation (a high cellar humidity value at a specified display limit is to be marked as a limited observation) and adds the key discriminator: capped reading versus usable measurement. The verb 'kennzeichnen' is somewhat abstract and the output of that marking is never stated, but the resource and intent are recognizable.

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 'Distinguish a capped humidity reading from a usable measurement' implies the situation in which the tool applies, but no explicit when-to-use condition, prerequisites, or comparison against a sibling (e.g. hygrometer_messbereiche or hygrometer_grenzuebertritt_zeitfenster) is given.

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