Skip to main content
Glama

getecoback-climate-weather

thermovorhang_heizkoerper_stoffkante

Read-only

Überdeckte Heizkörperbreite durch die geplante Stoffkante vor und nach Kürzung bestimmen — Find projected radiator overlap at the present and proposed curtain hem.

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": {
      "heizung_links_cm": "<heizung_links_cm>",
      "heizung_rechts_cm": "<heizung_rechts_cm>",
      "stoff_links_cm": "<stoff_links_cm>",
      "stoff_rechts_cm": "<stoff_rechts_cm>",
      "heizung_oben_cm": "<heizung_oben_cm>",
      "saum_alt_cm": "<saum_alt_cm>",
      "saum_neu_cm": "<saum_neu_cm>"
    },
    "name": "thermovorhang_heizkoerper_stoffkante"
  }
}

Input Schema

NameRequiredDescriptionDefault
saum_alt_cmYesUnterkante des vorhandenen Vorhangs ab Fußboden.
saum_neu_cmYesGeplante neue Unterkante ab Fußboden.
stoff_links_cmYesLinke Stoffkante entlang derselben Achse vor dem Heizkörper.
heizung_oben_cmYesOberkante des Heizkörpers ab Fußboden.
stoff_rechts_cmYesRechte Stoffkante.
heizung_links_cmYesLinke Heizkörperkante entlang der Wand.
heizung_rechts_cmYesRechte Heizkörperkante auf derselben Skala.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 calculation. The description adds that it compares present and proposed hem conditions, but it does not explain the return format, sign convention, or geometric assumptions, which matters because there is no output schema.

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 with no unnecessary operational fluff. The bilingual repetition is compact and does not obscure the purpose, though it is not especially structured for scanning.

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?

For a seven-required-parameter calculation tool with no output schema, the description is too thin. It states what is determined but not what is returned, how the two hem conditions are compared, or what assumptions about the geometry are made.

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 seven parameters are already documented in the schema. The description does not add parameter-level meaning beyond the schema, which is acceptable at the baseline level but not enriching.

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 ('bestimmen' / 'Find') and a specific resource: projected radiator overlap at the present and proposed curtain hem. It is not a tautology and the calculation purpose is clear, though it does not explicitly distinguish itself from related curtain or radiator tools.

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 guidance, no prerequisites, and no named alternative such as a curtain-fabric requirement tool. The phrase 'vor und nach Kürzung' implies it is used while planning a hem change, but the agent must infer that context.

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