Skip to main content
Glama

getecoback-climate-weather

innentuer_zugluftstopper_breite

Read-only

Eine abnehmbare Bodendichtung anhand der gemessenen Türöffnung und der notwendigen Luftwege beurteilen — Check draft-stopper coverage and clearance for an ordinary interior door.

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": {
      "tuerspalt_cm": "<tuerspalt_cm>",
      "abdeckung_cm": "<abdeckung_cm>",
      "bewegung_geprueft": "<bewegung_geprueft>",
      "luftweg_oder_sondertuer": "<luftweg_oder_sondertuer>"
    },
    "name": "innentuer_zugluftstopper_breite"
  }
}

Input Schema

NameRequiredDescriptionDefault
abdeckung_cmYesWirksame Breite der abnehmbaren Abdeckung.
tuerspalt_cmYesBreite des zu erfassenden Bodenspalts.
bewegung_geprueftYesTür lässt sich mit der geplanten Abdeckung vollständig und leicht öffnen?
luftweg_oder_sondertuerYesVorgesehener Luftweg oder Tür mit besonderer Funktion?

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?

The annotations already establish that this is a read-only, closed-world operation, and the description is consistent with an assessment/check rather than a mutation. It adds that coverage and clearance are checked based on measured door opening and air paths, but it does not explain the assessment criteria or what kind of result is produced.

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?

The definition is a single front-loaded sentence that states the assessment target and scope without filler. The bilingual German/English phrasing repeats the same content, but the duplication is modest and does not obscure the main instruction.

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?

The schema covers all required inputs, and the read-only annotation covers safety, so the basic invocation context is present. For an assessment tool with no output schema, however, the description does not explain what type of judgment is returned or how special-door cases relate to the 'ordinary interior door' scope.

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 the schema already documents all four parameters thoroughly. The description maps conceptually to the measured opening, coverage, and air paths, but adds little semantic detail beyond the schema, such as how movement or clearance is judged.

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 uses a specific verb, 'beurteilen', and a specific resource, 'abnehmbare Bodendichtung', and scopes it to an ordinary interior door. It is clear what the tool evaluates, though it does not explicitly distinguish itself from any named sibling alternative.

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 'for an ordinary interior door' gives an implied usage context and suggests a boundary against special doors. However, it does not explicitly state when not to use the tool, nor does it route special-door cases to another tool despite the parameter covering air paths or special-function doors.

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