Skip to main content
Glama

getecoback-climate-weather

tesa_tuerbodenprofil_belag_groesster_spalt

Read-only

Vergleicht den größten von drei senkrecht gemessenen Bodenspalten einer gewöhnlichen Zimmertür mit der deutschen tesa-Angabe für das konkrete Bodenprofil. — Compare the largest of three measured door-bottom gaps and the flooring with the German tesa profile specification.

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>",
      "gruppe": "<gruppe>",
      "belag": "<belag>",
      "bandseite_mm": "<bandseite_mm>",
      "mitte_mm": "<mitte_mm>",
      "griffseite_mm": "<griffseite_mm>"
    },
    "name": "tesa_tuerbodenprofil_belag_groesster_spalt"
  }
}

Input Schema

NameRequiredDescriptionDefault
belagYesFester Bodenbelag im Bereich der Dichtung.
gruppeYesArtikelgruppe laut deutscher Herstellerseite.
luftwegYesBeleg zur Funktion des Bodenspalts.
tuerartYesNutzung der konkreten Tür.
mitte_mmYesSenkrechter Spalt in der Mitte in mm.
bandseite_mmYesSenkrechter Spalt am Bandende in mm.
schutzstatusYesBeleg zur Schutzfunktion der konkreten Tür.
griffseite_mmYesSenkrechter Spalt am Griffende 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?

With readOnlyHint=true and openWorldHint=false already declaring the safety and locality profile, the description's added value is the aggregation rule that only the largest of the three gaps is used, which is real behavioral information affecting how inputs are prepared. However, it never says what the comparison yields (a verdict, a matched profile, a tolerance outcome) or what happens when the gap exceeds the specification. Useful but incomplete on outcome behavior.

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 single comparison statement is front-loaded and free of filler, but it is given twice verbatim (German then English), so roughly half the text is duplication with no new information. Appropriately short otherwise, with no wasted clauses beyond the bilingual repeat.

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?

This is an eight-required-parameter domain tool with five enums and no output schema, so the description carries the burden of explaining the returned result. It instead only restates the comparison, leaving an agent unable to predict whether it gets a boolean match, a recommended article group, or a failure condition. For a comparison/decision tool that is a substantive omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so per-parameter documentation is already handled, giving a baseline of 3. The description goes beyond it by explaining how bandseite_mm, mitte_mm and griffseite_mm relate: the comparison uses only the maximum of the three, which the schema never states. It also ties belag to 'the concrete floor profile' being looked up. That added relational meaning justifies a 4.

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 operation and operands: it compares the largest of three vertically measured door-bottom gaps against the German tesa specification for the given floor profile. This is far more specific than the opaque tool name (tesa_tuerbodenprofil_belag_groesster_spalt), which alone would tell an agent little. It stops short of distinguishing itself from the sibling tesa_tuerbodendichtung_montage_rueckstandsfrei, so it does not reach a 5.

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 scenario is implied rather than stated: an agent can infer it should call this when it has three gap measurements plus a flooring type and wants them checked against a tesa profile. There is no explicit 'use this when…', no exclusions, and no mention of the sibling tool that handles residual-free mounting. Usage is inferable but not guided.

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