Skip to main content
Glama

getecoback-raumklima

heizwaesche_nahmessung_gegen_lufttrend_fern

Read-only

Widersprüchliche Veränderungen nah am Ständer und am freien Raum-Messpunkt erkennen — Identify unresolved spatial moisture patterns instead of generalizing a local reading.

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": {
      "zeitlich_gepaart": "<zeitlich_gepaart>",
      "nahe_delta": "<nahe_delta>",
      "frei_delta": "<frei_delta>",
      "nahe_unsicherheit": "<nahe_unsicherheit>",
      "frei_unsicherheit": "<frei_unsicherheit>"
    },
    "name": "heizwaesche_nahmessung_gegen_lufttrend_fern"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_deltaYesÄnderung absoluter Feuchte am freien Raumpunkt in g/m³.
nahe_deltaYesÄnderung absoluter Feuchte nahe am Rack in g/m³.
zeitlich_gepaartYesSind beide Orte dokumentiert und ihre Änderungen aus exakt denselben Zeitpunkten abgeleitet?
frei_unsicherheitYesUnsicherheit der freien Änderung.
nahe_unsicherheitYesUnsicherheit der nahen Änderung.

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 conceptual context about detecting unresolved spatial patterns, but it does not describe what the tool returns or how uncertainty and temporal-pairing inputs affect the assessment.

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?

The definition is short and front-loaded, with the core comparison stated first. The German/English restatement is slightly redundant but not wasteful enough to obscure the purpose.

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-input analytical tool with no output schema, the description is adequate but incomplete. It does not explain what happens when 'zeitlich_gepaart' is false or how the uncertainty parameters influence whether a pattern is considered unresolved.

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 the schema already documents all five parameters in detail. The description reinforces the near-vs-free comparison but adds no threshold, pairing, or uncertainty semantics beyond what the schema provides.

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 gives a specific verb ('erkennen' / 'Identify') and a specific resource ('widersprüchliche Veränderungen nah am Ständer und am freien Raum-Messpunkt' / 'unresolved spatial moisture patterns'). It clearly scopes the tool to comparing near-rack and free-room readings, though it does not explicitly name a sibling alternative.

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 'instead of generalizing a local reading' implies when this tool should be preferred over a simpler local interpretation, but there is no explicit when-to-use, when-not-to-use, or named alternative. The required pairing flag 'zeitlich_gepaart' also suggests a prerequisite that the description never states.

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