Skip to main content
Glama

getecoback-climate-weather

klimageraet_serviceposition_markieren

Read-only

Verschiebeweg zum geplanten Servicepunkt gegen die real bemaßte freie Spur abgleichen — Check a straight repositioning distance for access to a switched-off portable unit.

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": {
      "geraet_tiefe_cm": "<geraet_tiefe_cm>",
      "spur_gesamt_cm": "<spur_gesamt_cm>",
      "verschiebung_cm": "<verschiebung_cm>",
      "spur_breite_geprueft": "<spur_breite_geprueft>",
      "verschieben_laut_handbuch": "<verschieben_laut_handbuch>"
    },
    "name": "klimageraet_serviceposition_markieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
spur_gesamt_cmYesFreie zusammenhängende Länge derselben Spur einschließlich Ausgangsfläche.
geraet_tiefe_cmYesLänge der Gerätefläche in geplanter Verschieberichtung.
verschiebung_cmYesGewünschter Versatz bis zur markierten Serviceposition.
spur_breite_geprueftYesAusreichende Spurbreite für das Gerät in dieser Ausrichtung vor Ort überprüft?
verschieben_laut_handbuchYesHandbuch erlaubt diesen geraden Versatz beim ausgeschalteten Gerät mit gelösten Anschlüssen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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, and the description correctly reads as a non-mutating validation. It adds the domain constraint being validated (straight shift distance vs. free track, unit powered off with connections loosened), but does not say what the check yields — pass/fail, message, or computed shortfall — which matters because no output schema exists.

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?

The description is short and front-loads the German statement of purpose, but the English sentence is a paraphrase rather than an addition, so roughly half the text is duplicated content. The phrasing is also dense to the point of being hard to parse on first read.

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 validation tool with no output schema, the definition covers the inputs via the schema but leaves the outcome contract and the handling of the two boolean attestation flags unexplained. An agent can form the call correctly but cannot predict or interpret the result.

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 a precise German definition (including bounds), so the schema already does the semantic work. The description only names the concept ('Verschiebeweg', 'freie Spur') without adding units, edge-case handling, or the meaning of a false boolean for the two verification flags.

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+resource pair: comparing the planned shift distance against the actually measured free track in order to reach a service position on a switched-off portable unit. That is concrete enough to distinguish it from the maintenance/logging siblings (Kondenswasser-Check, Ruhezeit, Geräuschmessung). It falls short of a 5 because the tool name ('Serviceposition markieren' — mark) and the described behavior ('abgleichen' — check) point in different directions, so an agent must reconcile name and description.

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?

The description states what the check does but never says when to reach for it, when not to, or what alternative to use. With a large sibling family of Klimagerät checks, no routing guidance is given at all — the agent must infer the trigger condition (before repositioning a unit) entirely on its own.

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