Skip to main content
Glama

getecoback-raumklima

innenverschattung_oberflaechenabstand_zur_raumluft

Read-only

Vergleicht beobachtete Temperaturabstände zur Raumluft an zwei erreichbaren Oberflächen rund um einen Behang — Compare measured surface-to-air temperature contrasts around a shade.

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": {
      "fensternahe_flaeche_c": "<fensternahe_flaeche_c>",
      "raumnahe_flaeche_c": "<raumnahe_flaeche_c>",
      "raumluft_c": "<raumluft_c>",
      "oberflaechen_vergleichbar": "<oberflaechen_vergleichbar>"
    },
    "name": "innenverschattung_oberflaechenabstand_zur_raumluft"
  }
}

Input Schema

NameRequiredDescriptionDefault
raumluft_cYesZeitgleiche Raumlufttemperatur im Schatten in °C.
raumnahe_flaeche_cYesVergleichbar gemessene zugängliche Fläche auf der Raumseite in °C.
fensternahe_flaeche_cYesVergleichbar gemessene zugängliche Fläche auf der Fensterseite in °C.
oberflaechen_vergleichbarYesGleiche Messmethode und bei Infrarotmessung geeignete Oberflächen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 values are observed/measured rather than modeled, but says nothing about what is computed, how mismatched measurements are handled, or what the comparison returns.

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 compact sentences with the substance front-loaded in the German line and a faithful English mirror. The bilingual duplication adds length but no ambiguity, and nothing is padded.

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?

Parameters are fully documented, but the tool has no output schema and the description never indicates what the comparison yields (e.g., which surface is warmer, magnitude, or verdict). For an analytic comparison tool, that leaves the agent guessing at 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%, so the baseline is 3. The description corroborates the two-surface-plus-room-air structure and the requirement that the measurements be comparable, but adds no format or plausibility detail beyond the schema.

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: it compares measured surface-to-air temperature contrasts at two accessible surfaces around a shade. That is more specific than a restatement of the name, but the term 'Behang' and the intended output remain opaque enough that an agent cannot fully predict the result.

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?

No when-to-use guidance, preconditions, or alternatives are given. The description does not say when this comparison is appropriate versus the neighboring room-air or shading tools, so selection must be inferred entirely from the name.

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