Skip to main content
Glama

getecoback-climate-weather

klimafenster_nasses_randbild_zeitfolge

Read-only

Ordnet Feuchtespuren an einer Fensterabdichtung zeitlich zu einem beobachteten Regenschauer ein — Relate visible seal moisture to a recorded rainfall timeline.

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": {
      "zuerst_nass_min": "<zuerst_nass_min>",
      "regen_start_min": "<regen_start_min>",
      "innen_und_aussen_getrennt": "<innen_und_aussen_getrennt>"
    },
    "name": "klimafenster_nasses_randbild_zeitfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
regen_start_minYesBeginn des beobachteten Regens in derselben Minute-Zählung in Minuten.
zuerst_nass_minYesErste bereits dokumentierte sichtbare Feuchte als Minute der Beobachtung in Minuten.
innen_und_aussen_getrenntYesWaren Raumseite und Außenseite im Protokoll unterscheidbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 agent knows this is a safe, closed-world analysis. The description adds the domain relation being computed, but does not disclose how the ordering is determined, what assumptions are made, or what the result contains.

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?

A single bilingual sentence, front-loaded with the German purpose and followed by the English equivalent. There is no redundant or filler wording.

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?

The tool is a read-only computation with three fully described parameters and no output schema. The description states the purpose but leaves the return value unexplained — whether the output is a delay, a sequence, or a per-event mapping — which is a notable gap when no output schema exists.

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 all three parameters are already documented in the schema. The description adds no parameter-specific meaning beyond what the schema provides, which is the baseline when schema coverage is complete.

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+resource: temporally relating visible moisture on a window seal to an observed rain shower. It is clear what the tool does, but it does not explicitly distinguish itself from the many sibling 'zeitfolge' tools beyond the domain objects involved.

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 by the description: use this when correlating seal moisture with a recorded rainfall timeline. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for cases where indoor and outdoor sides are not distinguishable.

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