Skip to main content
Glama

getecoback-climate-weather

tuerbodendoppeldichtung_05418_zwei_bodenseiten_abgleich

Read-only

Prüft den beidseitigen glatten Bodenbezug der deutschen tesa 05418 bei Belagwechsel über einer normalen Zimmertür. — Compare the flooring on both sides of an ordinary room door with the smooth-floor scope of the German tesa 05418 double seal.

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": {
      "tuerart": "<tuerart>",
      "schutzstatus": "<schutzstatus>",
      "luftweg": "<luftweg>",
      "seite_band": "<seite_band>",
      "seite_gegenueber": "<seite_gegenueber>"
    },
    "name": "tuerbodendoppeldichtung_05418_zwei_bodenseiten_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
luftwegYesBeleg zur Funktion des Bodenspalts.
tuerartYesNutzung der konkreten Tür.
seite_bandYesBelag auf der Öffnungsseite im betroffenen Bewegungsbereich.
schutzstatusYesBeleg zur Schutzfunktion der konkreten Tür.
seite_gegenueberYesBelag auf der Gegenseite im betroffenen Bewegungsbereich.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety and scope are covered structurally. The description adds the 'beidseitig' (both-sides) and 'normal room door' framing, but says nothing about how the enum value 'offen' is handled, whether a verdict or mismatch report is produced, or what a caller gets back.

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?

Two short sentences, purpose front-loaded, no filler or hedging. The German and English sentences are near-duplicates, which costs a little density, but the whole definition remains tight and scannable.

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 read-only assessment tool with five required enum parameters fully documented in the schema, the definition covers what the tool looks at. With no output schema, however, the description should at least indicate the shape of the result (a per-side comparison verdict versus a pass/fail), and it does 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 all five parameters are enums with their own descriptions, so the schema already carries the parameter semantics. The description adds no per-field meaning, such as how 'luftweg' interacts with 'schutzstatus' in the verdict, so the baseline of 3 applies.

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 concrete verb ('Prüft' / 'Compare') and a precise resource: the two-sided smooth floor contact of the German tesa 05418 at a flooring change over an ordinary room door. The scope is specific enough that an agent can distinguish it from generic comparison siblings, though it never names a sibling alternative to route against.

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?

The phrase 'bei Belagwechsel über einer normalen Zimmertür' implicitly states the situation in which the tool applies, which is useful context. However, there is no explicit when-not guidance, no prerequisites, and no pointer to any alternative tool for other door types or non-smooth floorings.

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