Skip to main content
Glama

getecoback-climate-weather

thermovorhang_paarprobe_scheibe_feuchte

Read-only

Zwei vergleichbare Wintermorgen auf sichtbare Feuchte am Vorhangfenster prüfen — Compare observed window moisture with the curtain open and closed.

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": {
      "vergleichbare_naechte": "<vergleichbare_naechte>",
      "offen_scheibe_c": "<offen_scheibe_c>",
      "geschlossen_scheibe_c": "<geschlossen_scheibe_c>",
      "offen_feucht": "<offen_feucht>",
      "geschlossen_feucht": "<geschlossen_feucht>"
    },
    "name": "thermovorhang_paarprobe_scheibe_feuchte"
  }
}

Input Schema

NameRequiredDescriptionDefault
offen_feuchtYesWar das Fenster innen bei offenem Vorhang sichtbar feucht?
offen_scheibe_cYesGemessene Scheibentemperatur mit geöffnetem Vorhang.
geschlossen_feuchtYesWar das Fenster innen bei geschlossenem Vorhang sichtbar feucht?
geschlossen_scheibe_cYesGemessene Scheibentemperatur mit geschlossenem Vorhang.
vergleichbare_naechteYesAußenlage, Innentemperatur, Lüftung und Nutzung vergleichbar?

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 safety is covered. The description adds one genuine behavioral constraint beyond that — the comparison is only valid across comparable winter mornings — but says nothing about what is returned or how the two observations are evaluated against each other.

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 short sentences with the core action front-loaded; nothing extraneous. Minor deduction for the German/English duplication, which repeats the same content rather than adding the second language's worth of new detail.

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 five-parameter observation tool with full schema documentation and no output schema, the description covers the essential purpose and the comparability precondition. It leaves open what the tool does with the paired values — the actual assessment logic — which is the remaining gap an agent might care about.

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 five required, well-described parameters (two boolean moisture observations, two bounded pane temperatures, one comparability flag). The description only restates the open/closed comparison concept and adds no syntax, units, or tolerance detail beyond the schema, so baseline 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 states a specific verb and resource: checking ('prüfen') visible moisture on the curtain window across two comparable winter mornings, with an explicit open-vs-closed curtain contrast. That is enough for an agent to distinguish this from the sibling thermal-curtain tools, though it does not name any alternative explicitly.

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 implied rather than stated: the 'zwei vergleichbare Wintermorgen' framing plus the required 'vergleichbare_naechte' flag signal that this tool is for controlled paired observations. There is no explicit when-to-use/when-not guidance or pointer to a related sibling tool for other curtain measurements.

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