Skip to main content
Glama

getecoback-climate-weather

hygrometer_umzug_erstes_stabiles_ablesefenster

Read-only

Prüfe nach einem Raumwechsel, welche Ablesung frühestens dem neuen Raum zugeordnet werden kann — Find the first usable reading after relocating a hygrometer

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": {
      "umzug_min": "<umzug_min>",
      "eigene_wartezeit_min": "<eigene_wartezeit_min>",
      "erstes_foto_min": "<erstes_foto_min>",
      "zweites_foto_min": "<zweites_foto_min>",
      "messort_markiert": "<messort_markiert>"
    },
    "name": "hygrometer_umzug_erstes_stabiles_ablesefenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
umzug_minYesMinute des Standortwechsels seit Beginn des Protokolls
erstes_foto_minYesMinute der ersten Ablesung nach dem Wechsel
messort_markiertYesMontagehöhe und genauer neuer Messpunkt eindeutig protokolliert
zweites_foto_minYesMinute der zweiten Ablesung nach dem Wechsel
eigene_wartezeit_minYesFür diesen Sensor festgelegte Wartezeit, wie im Versuch protokolliert

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. The description adds that the tool evaluates eligibility rather than merely reading data, but it does not say what the result looks like (a boolean verdict vs. a minute value) or how the waiting time interacts with the two photo timestamps.

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 with the condition ('nach einem Raumwechsel') front-loaded and no filler. The bilingual duplication costs a little space but is not wasteful, and no sentence is superfluous.

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 five-required-parameter, read-only computation with no output schema, the description leaves the return value and the decision rule (how waiting time, first and second photo, and the marked measurement point combine) unexplained. The annotations cover safety and the schema covers inputs, but the missing output contract keeps this at a merely adequate level.

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 of the five parameters carries its own German explanation with bounds, so the schema does the heavy lifting. The description only loosely maps to the inputs (relocation, first reading) and adds no interpretation of the required 'messort_markiert' flag or the two-photo sequence beyond what the schema states.

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 check ('Prüfe ... welche Ablesung frühestens dem neuen Raum zugeordnet werden kann') on a concrete resource — the first assignable hygrometer reading after a room change — and the English gloss confirms the same. It is clearly distinct from a plain reading or a location-check sibling, 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 trigger condition 'nach einem Raumwechsel' is stated, so an agent knows the situation in which to call it. There is no statement of when NOT to use it and no pointer to related tools such as the relocation evaluation or the measurement-point check, so routing among siblings is left to inference.

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