Skip to main content
Glama

getecoback-raumklima

punktwaerme_messraster_zonen_verteilung_spannweite

Read-only

Punktwärme an drei festen Nutzorten nach beobachteter räumlicher Gleichmäßigkeit einordnen — Identify nonuniform outcomes without averaging away a required spot.

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": {
      "platz_a_c": "<platz_a_c>",
      "platz_b_c": "<platz_b_c>",
      "platz_c_c": "<platz_c_c>",
      "ortsziel_c": "<ortsziel_c>",
      "abstand_max_c": "<abstand_max_c>",
      "messgroesse_und_zeit_gleich": "<messgroesse_und_zeit_gleich>"
    },
    "name": "punktwaerme_messraster_zonen_verteilung_spannweite"
  }
}

Input Schema

NameRequiredDescriptionDefault
platz_a_cYesSynchrone Temperatur am ersten verpflichtend genutzten Punkt.
platz_b_cYesSynchrone Temperatur am zweiten solchen Punkt.
platz_c_cYesSynchrone Temperatur am dritten solchen Punkt.
ortsziel_cYesEinheitliche selbst gewählte Untergrenze für alle drei Punkte.
abstand_max_cYesAkzeptierte größte Differenz zwischen den Punktmessungen.
messgroesse_und_zeit_gleichYesSind alle Beobachtungen dieselbe Temperaturmessgröße und derselbe Zeitpunkt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 one genuine behavioral trait beyond them: the result is per-spot and does not collapse the three readings into an average. It says nothing about the verdict produced, how the ortsziel lower bound and abstand_max spread jointly determine it, or what happens when messgroesse_und_zeit_gleich is false — and there is no output schema to fall back on.

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 bilingual sentence with no filler, and the operative constraint is placed in the English half where it reads as the key discriminator. The German half is dense jargon, but nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six required parameters, no output schema, and a comparison-based judgment task, the definition leaves the decisive logic unexplained: how the uniform lower bound and the accepted maximum spread combine into a classification, and how the synchrony boolean gates the result. For a tool whose whole value is the verdict, that is a significant omission.

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 every parameter is already documented with range and meaning; baseline 3 applies. The description only re-frames the three measurements as 'feste Nutzorte' with 'räumliche Gleichmäßigkeit' and adds no syntax, units, or interaction 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 German clause names a concrete operation (classifying point heat at three fixed use locations by observed spatial uniformity) rather than restating the tool name. The English gloss adds the differentiating intent — surfacing nonuniform outcomes instead of averaging a required spot — which separates it in spirit from the many punktwaerme siblings. It never names an actual sibling, so it stops short of a 5.

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 'without averaging away a required spot' phrasing hints at when this is preferred over an averaging-style check, but there is no explicit when-to-use, no prerequisites, and no named alternative. An agent must infer the scenario from the parameter set.

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