Skip to main content
Glama

getecoback-climate-weather

luftkuehler_ortsprobe_kuehler_und_schwuel_empfunden

Read-only

Hält persönlichen Kühlgewinn und Feuchtenachteil aus demselben Nass-Trocken-Vergleich getrennt fest — Separate felt cooling from perceived stuffiness in a matched wet/dry trial.

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": {
      "nass_lokal": "<nass_lokal>",
      "nass_raumgefuehl": "<nass_raumgefuehl>",
      "gleiche_nutzung": "<gleiche_nutzung>"
    },
    "name": "luftkuehler_ortsprobe_kuehler_und_schwuel_empfunden"
  }
}

Input Schema

NameRequiredDescriptionDefault
nass_lokalYesEigener Eindruck gegenüber trocken bei gleicher Luftbewegung.
gleiche_nutzungYesGleicher Sitzplatz, ähnliche Belastung und vergleichbares Zeitfenster?
nass_raumgefuehlYesGetrennter Eindruck der Raumluft.

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 and nothing contradicts it. The description adds a useful data-model point — the personal cooling gain and the room-air stuffiness disadvantage are stored separately rather than collapsed — but says nothing about what is persisted or returned after the call.

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 that leads with the separating action. The German/English duplication restates the same content twice, which is mild waste for an agent-facing definition but keeps the whole thing short.

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 three-parameter read-only recording tool with fully documented schema and no output schema, the description covers the intent adequately. It leaves open what the call produces and does not state that the matched-trial condition (gleiche_nutzung) must hold for the record to be meaningful.

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 enum fields already explain 'Eigener Eindruck gegenüber trocken' versus 'Getrennter Eindruck der Raumluft'. The description's Kühlgewinn/Feuchtenachteil framing roughly mirrors those definitions rather than adding new syntax or interpretation, so the baseline of 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 act (keeping two impressions apart / festhalten) and a specific scope (a matched wet/dry trial), which lets an agent distinguish it from the broader comparison and measurement siblings. It does not name any sibling explicitly, so the differentiation is inferential rather than stated.

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 only implied: the phrase 'aus demselben Nass-Trocken-Vergleich' signals that this belongs to a paired wet/dry observation. There is no explicit statement of when to call it instead of the neighbouring wet/dry or felt-air tools, and no prerequisite spelled out beyond the trial framing.

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