Skip to main content
Glama

getecoback-raumklima

wand_oberflaechenfaktor_abschaetzen

Read-only

Temperaturfaktor einer gemessenen Innenoberfläche bei stationären Bedingungen bestimmen — Calculate the measured surface-to-air temperature factor.

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": {
      "innen_c": "<innen_c>",
      "aussen_c": "<aussen_c>",
      "oberflaeche_c": "<oberflaeche_c>",
      "stabil": "<stabil>"
    },
    "name": "wand_oberflaechenfaktor_abschaetzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
stabilYesHinreichend stabile Bedingungen ohne Sonne, wechselndes Lüften oder starke zusätzliche Strahlungsquellen?
innen_cYesInnenluft in °C.
aussen_cYesAußenluft in °C.
oberflaeche_cYesInnenoberfläche in °C.

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 agent knows this is a safe, closed-world computation and behavioral risk is inherently low. The description adds that the calculation assumes steady-state conditions, which is meaningful context. It does not disclose the underlying relation (the f_Rsi ratio of surface-to-air temperature difference over indoor-outdoor difference) nor what the result looks like, which would have lifted this above baseline.

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 sentences, front-loaded with the German formulation and immediately followed by an English rendering. Efficient and unambiguous, though the bilingual duplication is strictly redundant for a reader who understands either language.

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?

All four required parameters are documented in the schema and the tool is a pure read-only computation, so nothing critical is missing for invocation. However, there is no output schema, and the description never says what is returned (a dimensionless factor, typically between 0 and 1) or how to interpret it, which is the main remaining gap for a calculation tool.

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%, with every parameter carrying a German label, unit and physical bounds, so the schema does the heavy lifting and baseline 3 applies. The description's mention of steady-state conditions loosely maps to the 'stabil' parameter but adds no new syntax or interpretation beyond the schema text. No meaning is added for innen_c, aussen_c or oberflaeche_c beyond what the schema 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?

The description names a concrete verb and a well-defined physical quantity: determining the temperature factor of a measured interior surface under steady-state conditions, restated in English as the surface-to-air temperature factor. An agent knows exactly what is being computed. It does not, however, position itself against related estimate tools (e.g. luftwechsel_dauer_abschaetzen or bauteil_waermeverlust), leaving the boundary implicit.

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 stationären Bedingungen' gives one precondition for use, and it is reinforced by the required 'stabil' flag. Beyond that there is no statement of when this tool is the right choice versus other estimation tools, and no explicit exclusions (e.g. dynamic/non-steady cases or transient measurements). Usage is implied rather than instructed.

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