Skip to main content
Glama

getecoback-climate-weather

duschhalter_fugenfeld_kontaktschablone_messband

Read-only

Für eine gemessene Saugnapf-Kontaktschablone prüfen, ob mögliche Fugenberührung schon aus der Messunsicherheit folgt — Bound a contact patch against one measured tile joint.

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": {
      "randabstand_mm": "<randabstand_mm>",
      "kontakthalbbreite_mm": "<kontakthalbbreite_mm>",
      "toleranz_mm": "<toleranz_mm>",
      "ganze_flaeche_geprueft": "<ganze_flaeche_geprueft>"
    },
    "name": "duschhalter_fugenfeld_kontaktschablone_messband"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_mmYesGemeinsame Unsicherheitsgrenze für beide Maße zusammen.
randabstand_mmYesKleinster senkrechter Abstand vom geplanten Mittelpunkt zur nächsten Fugenbegrenzung.
kontakthalbbreite_mmYesGemessener Abstand vom Mittelpunkt zum Rand des tatsächlichen Kontaktfelds in derselben Richtung.
ganze_flaeche_geprueftYesIst an der Stelle die ganze Kontaktkontur und die nächstliegende Fuge sichtbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 that the check is about whether contact already follows from measurement uncertainty (a conservative bound), which is useful, but it says nothing about what the tool returns or how the 'bound' decision is expressed.

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?

It is a single sentence with no filler, which is efficient, but the German compound phrasing and the em-dash English gloss read as compressed and slightly cryptic. It is front-loaded but not immediately parseable for an agent skimming tool descriptions.

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 four required parameters and no output schema, the description should ideally state what the check returns (e.g., whether contact is possible/guaranteed or how much margin remains). It conveys the purpose but leaves the result semantics and the significance of ganze_flaeche_geprueft to inference, which is a gap for a no-output-schema 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 (Randabstand, Kontakthalbbreite, Toleranz, ganze Fläche geprüft) are already documented with ranges and meaning. The description adds the notion that Toleranz is a shared uncertainty bound for both measures, but does not explain parameter interactions or the role of ganze_flaeche_geprueft beyond the schema.

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 description names a concrete resource (Saugnapf-Kontaktschablone / contact patch vs. one measured tile joint) and a specific operation (bounding/checking whether joint contact follows from measurement uncertainty). However, the wording is a dense German noun pile plus a partial English restatement, and it does not distinguish this check from other Duschhalter/Messband siblings or state what a positive/negative result means.

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, no prerequisites, and no reference to an alternative sibling tool. An agent can infer that this is a measurement-uncertainty bounding check, but nothing tells it when this tool is preferable to the related contact/measurement 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