Skip to main content
Glama

getecoback-raumklima

monoblock_schlauch_sichtstrecke_ohne_doppelzaehlung

Read-only

Ermittelt sichtbare und noch ungeklärte Schlauchlänge aus zwei teilweise überlappenden Sichtaufnahmen — Account for visible and unseen hose lengths across two overlapping observations.

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": {
      "gesamter_verlauf_mm": "<gesamter_verlauf_mm>",
      "sichtbar_a_mm": "<sichtbar_a_mm>",
      "sichtbar_b_mm": "<sichtbar_b_mm>",
      "ueberlappung_mm": "<ueberlappung_mm>"
    },
    "name": "monoblock_schlauch_sichtstrecke_ohne_doppelzaehlung"
  }
}

Input Schema

NameRequiredDescriptionDefault
sichtbar_a_mmYesIn Aufnahme A sichtbare Länge entlang der Mitte in mm.
sichtbar_b_mmYesIn Aufnahme B sichtbare Länge in mm.
ueberlappung_mmYesNachweislich in beiden Aufnahmen sichtbare Strecke in mm.
gesamter_verlauf_mmYesDokumentierte Länge entlang der Mitte des vorhandenen Schlauchs in mm.

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. The description adds the useful context that the result is derived by reconciling two overlapping views (i.e. the overlap must not be double-counted), but says nothing about what happens with inconsistent inputs, whether unexplained length is flagged or errors are raised, or what shape the answer takes.

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 operative content is front-loaded in a single clause pair, which is good. However, the sentence is given twice in German and English with no additional information in either version, so roughly half the text is redundant padding rather than earning its place.

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?

Inputs are fully required and fully documented in the schema, but there is no output schema, so the description carries the burden of explaining what is returned. It only vaguely gestures at 'sichtbare und noch ungeklärte Schlauchlänge' without clarifying whether that is one value, a pair, or a breakdown, leaving a real gap for a computation 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 four parameters are already documented in the schema. The description's only added semantics is that sichtbar_a_mm and sichtbar_b_mm are partially overlapping views and that ueberlappung_mm exists to reconcile them; it does not explain how gesamter_verlauf_mm bounds the result or how the arithmetic combines the inputs, so it stays at the baseline.

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 names a specific operation (Ermittelt / compute) on a specific resource (sichtbare und ungeklärte Schlauchlänge) and states the input condition (zwei teilweise überlappenden Sichtaufnahmen). An agent can tell this is a length-reconciliation computation rather than a plain read or a settings change. It stops short of differentiating itself from the similar-sounding sibling monoblock_schlauch_sichtform_achsenvergleich.

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?

Usage is only implied: the phrase 'aus zwei teilweise überlappenden Sichtaufnahmen' signals the precondition that two overlapping observations must exist. There is no explicit when-to-use, when-not-to-use, or alternative named, so the agent must infer applicability from the overlap wording.

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