Skip to main content
Glama

getecoback-climate-weather

gebraucht_dichtung_zugangsabschnitte_sichtbefund

Read-only

Sichtbare Dichtungsabschnitte einer Behälteröffnung nach fehlender Ansicht und Auffälligkeit bilanzieren — Keep obscured portions out of a visual gasket inspection.

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": {
      "sichtpruefung_zulaessig": "<sichtpruefung_zulaessig>",
      "laenge_cm": "<laenge_cm>",
      "verdeckt_cm": "<verdeckt_cm>",
      "sichtspur_cm": "<sichtspur_cm>",
      "probe_im_gebrauch_gezeigt": "<probe_im_gebrauch_gezeigt>"
    },
    "name": "gebraucht_dichtung_zugangsabschnitte_sichtbefund"
  }
}

Input Schema

NameRequiredDescriptionDefault
laenge_cmYesAm zugänglichen Verlauf markierte Gesamtstrecke in cm.
verdeckt_cmYesDavon nicht beurteilbare Strecke in cm.
sichtspur_cmYesWeitere Strecke mit tatsächlich sichtbarer Auffälligkeit in cm.
sichtpruefung_zulaessigYesIst die sichtbare Dichtung der vorgesehenen zugänglichen Öffnung ohne Eingriff erkennbar?
probe_im_gebrauch_gezeigtYesWurde die identische Öffnung zusätzlich bei zulässigem normalen Gebrauch beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral rule beyond the annotations: obscured portions must be excluded from the visual inspection, which explains why verdeckt_cm is subtracted rather than counted. It does not say what happens when sichtpruefung_zulaessig is false, which keeps it from a 5.

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?

One front-loaded sentence with a supporting constraint clause, no filler or repetition. It is dense in German nominal style but every part carries meaning. A short statement of the computed result would have been a better use of the space than the phrasing 'nach fehlender Ansicht und Auffälligkeit'.

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?

With five required parameters and no output schema, the description should tell the agent what the balance actually returns (a ratio, a count, a verdict). It explains the exclusion rule but leaves the result shape undefined. The fully documented schema compensates for the parameter side, so this is adequate rather than complete.

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 five parameters are already documented in the schema, which sets the baseline at 3. The description restates the two concepts behind the parameters (fehlende Ansicht, Auffälligkeit) but adds nothing about units, ranges, or how the two lengths interact.

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 action on a specific object: tallying ('bilanzieren') the visible gasket sections of a container opening by missing view and conspicuousness. That is more than a restatement of the name. It stops short of 5 because the exact result of the tally is not stated and nothing distinguishes this tool from its many gebraucht/_gebraucht siblings.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The second clause ('Keep obscured portions out of a visual gasket inspection') is a validity rule for the calculation, not a routing instruction, so an agent gets no help deciding when to call this instead of the related inspection tools.

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