Skip to main content
Glama

getecoback-climate-weather

fensterwasser_abgrenzung_regen_zeitstempel

Read-only

Eine nasse Fensterbank zwischen beobachtetem Regenkontakt und Reinigungsphase zeitlich einordnen — Flag overlapping sources before comparing a wet windowsill.

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": {
      "putz_ab": "<putz_ab>",
      "putz_bis": "<putz_bis>",
      "regen_ab": "<regen_ab>",
      "regen_bis": "<regen_bis>",
      "nass_ab": "<nass_ab>",
      "nass_bis": "<nass_bis>",
      "randbedingungen_belegt": "<randbedingungen_belegt>"
    },
    "name": "fensterwasser_abgrenzung_regen_zeitstempel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nass_abYesFrühester Zeitpunkt der eigenen Nassbeobachtung.
putz_abYesBeginn beobachteter Reinigungsphase.
nass_bisYesLetzte Minute dieses beobachteten Abschnitts.
putz_bisYesEnde beobachteter Phase.
regen_abYesBeginn beobachteten Außenwasserkontakts.
regen_bisYesEnde dieses Kontakts.
randbedingungen_belegtYesGleicher Tag und gleicher Fensterbereich mit bekannten Zeitgrenzen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety profile is covered and nothing in the description contradicts it. The description adds that the operation is a comparison/flagging over observed intervals rather than a measurement, but with no output schema it never explains what the flag looks like or how ties/zero-length intervals are treated.

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?

Two short sentences, so nothing is bloated, but the second sentence half-repeats the first in another language and mixes registers ('Flag overlapping sources' vs. the German framing). The key concept — that overlaps between rain and cleaning intervals are what get flagged — is buried in the trailing clause.

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?

All seven parameters are required and fully documented in the schema, so an agent can construct a call. However, with no output schema the description should clarify what the tool returns (a flag? an ordering?), and it never explains how nass_ab/nass_bis relate to the two comparison intervals beyond being 'own observations'.

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 seven parameters (including the 0–1440 minute bounds and the randbedingungen_belegt precondition) are already self-documenting; baseline is 3. The description only loosely frames regen_* and putz_* as the two 'sources' being compared, adding little beyond the schema.

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 German clause names a concrete operation (temporally situating a wet windowsill between observed rain contact and a cleaning phase), but the English addendum shifts the framing to 'flag overlapping sources', so the actual output/action is ambiguous. The resource is identifiable; the verb is not consistently stated, and no sibling tool is named for differentiation.

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?

'before comparing a wet windowsill' gives a single sequencing hint, which is the only usage context offered. There is no statement of when NOT to use it, no prerequisites (e.g. that all intervals must be same-day, same window area), and no routing to any alternative tool.

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