Skip to main content
Glama

getecoback-raumklima

heizkoerper_reflektor_flaechenbedarf

Read-only

Das gemessene freie Wandfeld hinter einem Heizkörper mit dem verfügbaren Reflektorformat vergleichen — Size reflector material for a single unobstructed rectangular wall patch.

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": {
      "wandfeld_breite_cm": "<wandfeld_breite_cm>",
      "wandfeld_hoehe_cm": "<wandfeld_hoehe_cm>",
      "folie_breite_cm": "<folie_breite_cm>",
      "folie_laenge_cm": "<folie_laenge_cm>",
      "drehbar": "<drehbar>"
    },
    "name": "heizkoerper_reflektor_flaechenbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
drehbarYesDas Produkt und der Zuschnitt dürfen laut Unterlagen in beiden Richtungen verwendet werden?
folie_breite_cmYesNutzbare Rollenbreite nach Randverlust.
folie_laenge_cmYesNutzbare zugeschnittene Länge der verfügbaren Folie.
wandfeld_hoehe_cmYesHöhe desselben Felds ohne Halterungen und Ventil.
wandfeld_breite_cmYesBreite des tatsächlich freien rechteckigen Felds hinter dem Heizkörper.

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 mark it read-only and closed-world. The description adds the important constraint that only a single unobstructed rectangular patch is handled, but it does not explain what the comparison returns or how the rotatability flag affects the result.

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 bilingual clauses with the action front-loaded and little wasted text. The German/English duplication is slightly redundant but still efficient and readable.

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 description gives enough scope to know what input situation the tool handles, and annotations clarify safety. However, with no output schema and no stated return value, an agent cannot tell whether the result is a fit decision, required area, or cut layout.

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 coverage is 100%, so all five parameters, including the rotatability flag and usable film dimensions, are already documented in the schema. The description adds no parameter-level meaning beyond restating the comparison/scope.

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?

States a specific action: comparing the measured free rectangular wall patch behind a radiator against available reflector format, with the English clause clarifying it as sizing reflector material. The narrow scope makes it distinguishable, though it does not explicitly name an alternative sibling.

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?

Usage is implied by 'single unobstructed rectangular wall patch,' which tells the agent the geometry must be one free rectangle. It does not state when to choose this over other radiator/reflector checks or any exclusions beyond that.

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