Skip to main content
Glama

getecoback-raumklima

sitzplatz_operative_temperatur_einordnen

Read-only

Luft- und mittlere Strahlungstemperatur am Sitzplatz als Komfortorientierung zusammenführen — Estimate operative temperature under low air movement.

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": {
      "luft_c": "<luft_c>",
      "mittlere_strahlung_c": "<mittlere_strahlung_c>",
      "geringe_luftbewegung": "<geringe_luftbewegung>"
    },
    "name": "sitzplatz_operative_temperatur_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
luft_cYesGemessene Lufttemperatur am gewählten Platz, nicht an einem Sonnentreffer.
geringe_luftbewegungYesGeringe Luftbewegung und keine direkte intensive Strahlungsquelle am Messplatz?
mittlere_strahlung_cYesSeparat ermittelte mittlere Strahlungstemperatur am gleichen Platz, nicht eine einzelne Wand.

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 safety is covered. The description adds that the result is an 'Estimate' for comfort orientation rather than a measured value, which is useful framing, but it does not say how the two inputs are combined, what precision to expect, or that the low-air-movement boolean gates the validity of 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?

A single front-loaded sentence states the inputs and the output, with the qualifying condition trailing it. Nothing is wasted, though the mixed German/English phrasing is slightly awkward and the sentence is terse to the point of omitting the output unit.

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?

For a simple read-only three-parameter estimator this is close to sufficient, but with no output schema the description should at least indicate that the return is a single operative temperature value and in what unit. It also leaves the estimation logic opaque, which matters when the result feeds comfort judgements.

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 the parameter descriptions are already rich (measured at the seat, not at a sun patch; mean radiant temperature from the same spot, not a single wall). The description adds only the conceptual link that the boolean encodes the low-air-movement assumption, so the baseline 3 applies.

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 specific verb and resource: combining air temperature and mean radiant temperature at a seat to estimate operative temperature, with the low-air-movement caveat. It is clear what the tool computes, but it never distinguishes itself from the many sibling temperature tools (e.g. raumtrennung_mischszenario_temperatur, arbeitszimmer_abwaerme_vergleich).

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 the phrase 'als Komfortorientierung' and by the required low-air-movement condition, which tells the agent the estimate only applies in still-air settings. There is no explicit statement of when to prefer this tool over a sibling or when it must not be used (e.g. high air movement or direct solar load).

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