Skip to main content
Glama

getecoback-raumklima

heizwaesche_luftprobe_zeitpunkt_einem_abschnitt_zuordnen

Read-only

Eine nachträglich notierte Raummessung bei begrenzter Uhrzeitunsicherheit richtig einer Rack-Phase zuordnen — Check whether a moisture reading could straddle a phase boundary.

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": {
      "uhr_gemeinsam": "<uhr_gemeinsam>",
      "phase_ab": "<phase_ab>",
      "phase_bis": "<phase_bis>",
      "geschaetzt_min": "<geschaetzt_min>",
      "plus_minus": "<plus_minus>"
    },
    "name": "heizwaesche_luftprobe_zeitpunkt_einem_abschnitt_zuordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
phase_abYesWirklicher Beginn der beobachteten Phase (inklusive).
phase_bisYesErste Minute außerhalb dieser Phase.
plus_minusYesMaximale Abweichung dieser Uhrzeit in Minuten.
uhr_gemeinsamYesSind Phasen und Messzeit auf derselben Uhrzeitskala dokumentiert?
geschaetzt_minYesGeschätzte Uhrzeit der Messung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the useful behavioural hint that the result concerns whether a reading could straddle a phase boundary, but it does not say what the answer looks like (a phase label, a boolean, an ambiguity flag).

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

Conciseness3/5

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

It is short and front-loads the German framing, but the English sentence largely restates the German one instead of extending it, and the second half ('Check whether a moisture reading could straddle a phase boundary') shifts topic without adding new operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five required parameters and no output schema mean the description must explain the returned judgement, and it does not — an agent cannot tell whether the tool returns the assigned phase, a boundary-straddle verdict, or both. It also never states the shared-clock precondition implied by uhr_gemeinsam, leaving a real gap for a decision 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%, so all five parameters (phase_ab, phase_bis, geschaetzt_min, plus_minus, uhr_gemeinsam) are already documented in the schema. The description adds only the general framing of clock uncertainty and boundary checking, not per-parameter meaning.

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 states a concrete operation: assigning a retrospectively noted room moisture reading with bounded clock uncertainty to a rack phase, and it adds the boundary-straddle check. That is a specific verb-plus-resource, though the German/English duplication repeats the same idea rather than sharpening it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the many sibling phase/measurement tools, no prerequisites (e.g., that phase times and reading time must share a clock), and no exclusions. The only implied usage comes from the phrase 'nachträglich notierte'.

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