Skip to main content
Glama

getecoback-climate-weather

dachraum_luftvolumen_aufmass

Read-only

Bei einer durchgehenden Dachschräge mittlere Höhe und Raumvolumen aus dem Aufmaß bestimmen — Calculate room air volume under one planar sloped ceiling.

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": {
      "bodenflaeche_m2": "<bodenflaeche_m2>",
      "hohe_seite_m": "<hohe_seite_m>",
      "niedrige_seite_m": "<niedrige_seite_m>",
      "einheitliche_schraege": "<einheitliche_schraege>"
    },
    "name": "dachraum_luftvolumen_aufmass"
  }
}

Input Schema

NameRequiredDescriptionDefault
hohe_seite_mYesLichte Höhe am hohen Rand in Metern.
bodenflaeche_m2YesRechteckige Grundfläche unter der Schräge.
niedrige_seite_mYesLichte Höhe am niedrigen parallelen Rand in Metern.
einheitliche_schraegeYesEine durchgehende ebene Schräge zwischen parallelen Kanten ohne Absätze?

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 the safety profile is covered. The description adds that the tool derives two intermediate/derived quantities (mean height and volume), but does not say what happens when einheitliche_schraege is false, nor the units or precision of the returned values. Given annotation coverage, this is adequate but thin.

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?

A single, front-loaded sentence whose core computation is stated before the constraint. The German/English duplication is mild redundancy but aids clarity rather than obscuring it.

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?

With four required, fully documented numeric/boolean parameters and no output schema, the description does most of what is needed. However, it never states the units or shape of the result (m³, m), which matters precisely because no output schema exists to convey the return value.

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 every parameter carries a unit-bearing description in the schema, so the baseline is 3. The prose adds no syntax, range, or edge-case guidance beyond what the schema already states.

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?

Names a specific computation (mean height and room volume) from a specific input situation (a single continuous planar sloped ceiling), stated in both German and English. The phrase 'one planar sloped ceiling' implicitly scopes it away from multi-plane or non-continuous roof geometry, though no sibling is named.

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 clause 'Bei einer durchgehenden Dachschräge' functions as a precondition for use, but there is no explicit when-not guidance and no named alternative tool for other roof geometries. Usage is only implied by the geometric precondition, which is also encoded in the einheitliche_schraege parameter.

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