Skip to main content
Glama

getecoback-climate-weather

hygrometer_messbereiche

Read-only

Zwei Hygrometer mit ihren angegebenen Genauigkeiten vergleichen — Check whether two humidity readings overlap within stated measurement tolerances.

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": {
      "reading_a_pct": "<reading_a_pct>",
      "accuracy_a_pp": "<accuracy_a_pp>",
      "reading_b_pct": "<reading_b_pct>",
      "accuracy_b_pp": "<accuracy_b_pp>"
    },
    "name": "hygrometer_messbereiche"
  }
}

Input Schema

NameRequiredDescriptionDefault
accuracy_a_ppYesAngegebene absolute Toleranz des ersten Geräts in Prozentpunkten.
accuracy_b_ppYesAngegebene absolute Toleranz des zweiten Geräts in Prozentpunkten.
reading_a_pctYesRelative Feuchte der Raumluft in Prozent.
reading_b_pctYesRelative Feuchte der Raumluft in Prozent.

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the core semantics of the computation (tolerance-interval overlap), but does not disclose the result form — boolean verdict, overlap range, or margin — which matters because there is no output schema.

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 action. The German and English halves are largely duplicative, which is slightly wasteful, but neither contains filler or hedging.

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 numeric parameters, no output schema, and a purely computational tool, the definition should say what a caller receives back and how boundary/touching intervals are treated. It conveys the question being answered but leaves the return value and boundary behavior unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including units (percent relative humidity, percentage points of tolerance) and ranges is already documented. The description only restates that accuracies are 'stated measurement tolerances', adding no new meaning, which is the expected baseline-plus case.

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 verb and resource ('zwei Hygrometer ... vergleichen' / 'check whether two humidity readings overlap') and states the comparison criterion, tolerance overlap. It is clearly distinct from sibling hygrometer_messort_pruefen, though it does not name any sibling explicitly.

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 use case is implied by the phrasing — compare two devices' stated accuracies to see whether their readings are mutually consistent. There is no explicit guidance on when to prefer this over other hygrometer-related siblings, nor any stated preconditions (e.g. that both accuracies must be manufacturer-stated values).

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