Skip to main content
Glama

getecoback-climate-weather

nachtlueften_windmittel_und_boeen

Read-only

Windmittel und stärkste Böe einer Nachtlüftungsprobe getrennt ins Protokoll übernehmen — Compare a recorded wind average and gust without assigning a window safety rating.

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": {
      "mittel_kmh": "<mittel_kmh>",
      "boee_kmh": "<boee_kmh>",
      "selber_abschnitt": "<selber_abschnitt>",
      "richtung_am_fenster_beobachtet": "<richtung_am_fenster_beobachtet>"
    },
    "name": "nachtlueften_windmittel_und_boeen"
  }
}

Input Schema

NameRequiredDescriptionDefault
boee_kmhYesStärkste gemeldete Böe für diesen Abschnitt in km/h.
mittel_kmhYesWindmittel für den protokollierten Abschnitt in km/h.
selber_abschnittYesDieselbe Zeit, Quelle und Einheit für beide Windwerte?
richtung_am_fenster_beobachtetYesWurde die tatsächliche Strömungsrichtung am Fenster beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds that the tool only compares recorded values and deliberately avoids a safety-rating judgment. It does not describe the comparison output or validation behavior, but this is useful extra context for a read-only analytical tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single compact sentence with the core comparison front-loaded and the safety-rating boundary appended. There is no redundant wording.

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

Completeness4/5

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

Four required parameters are fully documented in the schema, and the read-only annotations cover the safety profile, so the description supplies the remaining purpose and scope boundary. It does not explain the comparison result, but with no output schema that is a minor 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%, with all four required parameters documented in the schema. The description restates the wind average and gust concepts but adds no new meaning for the boolean parameters selber_abschnitt or richtung_am_fenster_beobachtet.

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?

States a specific action and resource: comparing a recorded wind average and gust from a night-ventilation sample. It also sets a clear scope boundary by saying no window safety rating is assigned, though it does not name a specific sibling alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage context and an explicit exclusion: use it to compare wind average and gust, not to assign a window safety rating. It does not name alternative tools or explain when another sibling should be preferred.

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