Skip to main content
Glama

getecoback-climate-weather

rollwagen_parkprobe_geraet_gegen_grundrahmen

Read-only

Trennt Verschiebung des Wagens von einer beobachteten Verschiebung des Gehäuses relativ zum Wagen — Compare apparent relative motion between a parked appliance and the base.

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_vor_mm": "<geraet_vor_mm>",
      "rahmen_vor_mm": "<rahmen_vor_mm>",
      "geraet_nach_mm": "<geraet_nach_mm>",
      "rahmen_nach_mm": "<rahmen_nach_mm>",
      "aufloesung_mm": "<aufloesung_mm>",
      "messbezug_gleich": "<messbezug_gleich>"
    },
    "name": "rollwagen_parkprobe_geraet_gegen_grundrahmen"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufloesung_mmYesEigene Auflösung oder Ablesebreite in mm.
geraet_vor_mmYesAblesung an Gehäusemarke zu Beginn in mm.
rahmen_vor_mmYesAblesung an Rahmenmarke zu Beginn in mm.
geraet_nach_mmYesAblesung an Gehäusemarke danach in mm.
rahmen_nach_mmYesAblesung an Rahmenmarke danach in mm.
messbezug_gleichYesDieselbe Achse, beide Marken und stationäre dokumentierte Beobachtungsbedingungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish readOnlyHint=true and openWorldHint=false (a safe, closed-world computation), so safety is covered. What the description does not disclose is the behavior that matters: what the tool returns (a corrected displacement? a discrepancy indication?), and crucially how the boolean gate 'messbezug_gleich' conditions or invalidates the result — a key behavioral trait for a pure calculation tool with no output schema.

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?

A single front-loaded German sentence followed by a compact English gloss — no filler. It is efficiently structured; the only cost is that the brevity comes at the expense of substance rather than being wasteful in wording.

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?

For a six-required-parameter computation tool with no output schema and no sibling differentiation, the description is too thin: it neither explains the returned values nor clarifies the precondition semantics of messbezug_gleich. Since no output schema exists, the definition carried the burden of describing the result and did not.

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 six parameters carries its own German explanation (readings at housing mark / frame mark, before and after, resolution, same-reference flag), so the schema does the heavy lifting. The description adds only a general framing and no extra meaning about how the numbers are combined, which is the expected baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The bilingual gloss ('Trennt Verschiebung des Wagens von einer beobachteten Verschiebung des Gehäuses relativ zum Wagen') does convey the conceptual idea of separating trolley displacement from apparent housing displacement, but the verb is abstract and the description never says this is a before/after reading computation. With the name alone being opaque jargon, the definition leaves the concrete operation ('compare two mark readings and return the corrected delta') implicit, and it does not distinguish itself from any sibling.

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 when-to-use, when-not-to-use, or alternative-tool guidance at all. It does not say when a parked-appliance relative-motion check is the right tool versus the many other rollwagen_* and geraet_* comparison tools listed as siblings, so an agent must guess from the name.

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