Skip to main content
Glama

getecoback-climate-weather

wetterquelle_standort_messvergleich

Read-only

Stationswetter und Messung vor deinem Fenster nach Standorteignung dokumentieren — Choose the defensible source for a window-side observation.

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": {
      "quelle": "<quelle>",
      "aussenfuehler_verschattet": "<aussenfuehler_verschattet>",
      "zeitstempel_passend": "<zeitstempel_passend>",
      "fensterseite_gemessen": "<fensterseite_gemessen>"
    },
    "name": "wetterquelle_standort_messvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelleYesDeklarierte Quelle.
zeitstempel_passendYesLiegt der Wert für die gewünschte Stunde und nicht für ein Tagesmaximum vor?
fensterseite_gemessenYesErfasst die Messung die tatsächliche Fensterseite?
aussenfuehler_verschattetYesEigener Außenfühler belüftet und im Schatten, nicht an aufgeheizter Fläche?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 no behavior beyond that: it does not say what the tool produces (a verdict, a ranked source, a documentation record), how the four booleans influence the outcome, or what happens when a check fails.

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

Conciseness3/5

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

The description is short, but it is two loosely parallel clauses in different languages that restate each other rather than front-loading a single clear statement of function. No sentence is clearly wasted, yet the structure obscures rather than clarifies.

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 four required parameters, no output schema, and a selection/judgment task, the description should explain what decision is produced and how the inputs combine. It does not, so an agent knows the theme but not the contract of the call.

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 parameters documented and an enum on 'quelle', so the schema carries the parameter meaning. The description adds nothing about how 'aussenfuehler_verschattet' or 'zeitstempel_passend' are used in judging suitability, leaving the baseline score appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description combines a vague German clause about documenting station weather and window-side measurements with an English tagline about choosing a 'defensible source'. It gestures at the resource (weather/measurement source selection) but never states concretely what the tool does or returns, so an agent cannot cleanly separate it from siblings like heizfuehler_standort or nachtabsenkung_messvergleich.

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?

There is an implied context ('window-side observation', 'Standorteignung') but no explicit when-to-use statement, no prerequisites, and no named alternative that would select a different tool. The agent must infer the triggering situation entirely.

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