Skip to main content
Glama

getecoback-raumklima

hygrometer_messpunkt_markierung_versatz

Read-only

Auf der Planskizze prüfen, ob ein Messpunkt nach einer Umstellung am alten Ort blieb — Compute marked sensor position displacement before combining a time series.

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": {
      "alt_x_cm": "<alt_x_cm>",
      "alt_y_cm": "<alt_y_cm>",
      "alt_hoehe_cm": "<alt_hoehe_cm>",
      "neu_x_cm": "<neu_x_cm>",
      "neu_y_cm": "<neu_y_cm>",
      "neu_hoehe_cm": "<neu_hoehe_cm>",
      "toleranz_cm": "<toleranz_cm>"
    },
    "name": "hygrometer_messpunkt_markierung_versatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_x_cmYesUrsprünglicher X-Abstand zu einer festen Raummarke.
alt_y_cmYesUrsprünglicher Y-Abstand zu derselben Marke.
neu_x_cmYesNeuer X-Abstand bei gleicher Achsenlage und Raummarke.
neu_y_cmYesNeuer Y-Abstand.
toleranz_cmYesEigene Positionstoleranz für die wiederholte Aufstellung.
alt_hoehe_cmYesUrsprüngliche Höhe des Sensors über Boden.
neu_hoehe_cmYesNeue Sensorhöhe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 structurally. The description adds useful workflow context (a pre-combination consistency check against a plan sketch) but says nothing about how the tolerance is applied, what happens when displacement exceeds it, or what the caller receives, and no output schema exists to fill that gap.

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?

Two clauses, no padding, and the trigger condition is placed at the end rather than front-loaded. The abrupt switch from German to English within a single sentence makes the intent harder to parse than a consistently worded statement would.

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?

Seven required parameters and no output schema mean the description has to carry more weight than it does: the agent learns the purpose and timing but not what the result looks like or what the tolerance outcome means. For a read-only, closed-world calculation this is adequate but leaves a real gap around the returned displacement verdict.

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% for all seven numeric parameters, so the baseline of 3 applies. The description adds no meaning beyond the schema – in particular it does not explain how toleranz_cm is compared against the old/new coordinate deltas, which is the one semantic point the schema cannot convey on its own.

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 specific computation on a specific resource: displacement of a marked sensor measurement point between an old and a new position. The German clause adds the concrete check (did the point stay at the old location after a relocation), which an agent can distinguish from siblings like hygrometer_messort_pruefen. It stops short of explicitly naming how it differs from those neighbouring tools.

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 'before combining a time series' gives one real precondition for calling it, which is more than a bare purpose statement. However, no alternative tool is named, no when-not condition is given, and the sibling that also deals with measurement-point verification is left implicit.

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