Skip to main content
Glama

getecoback-climate-weather

regen_fleck_wiederkehr_ereignisvergleich

Read-only

Zwei Regenereignisse und einen trockenen Kontrollzeitraum im Feuchteprotokoll vergleichen — Check recurrence after rain without identifying a building defect.

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": {
      "nach_regen_a": "<nach_regen_a>",
      "nach_regen_b": "<nach_regen_b>",
      "im_trockenen_vergleich": "<im_trockenen_vergleich>",
      "zeiten_gleich": "<zeiten_gleich>",
      "innenquellen_protokolliert": "<innenquellen_protokolliert>"
    },
    "name": "regen_fleck_wiederkehr_ereignisvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
nach_regen_aYesMarkierung an derselben Stelle im festgelegten Beobachtungsfenster nach Regen A neu oder stärker?
nach_regen_bYesDieselbe Beobachtung nach Regen B?
zeiten_gleichYesGleich lange Beobachtungszeitfenster und gleiche sichtbare Stelle?
im_trockenen_vergleichYesDieselbe Beobachtung im trockenen Vergleichszeitraum?
innenquellen_protokolliertYesLüften, Wäsche, Kochen und andere Innenquellen protokolliert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 a genuine behavioral boundary beyond that: the tool performs a correlational comparison and does not establish a building defect, which tells the agent how to interpret the result. It stops short of saying what form the comparison result takes.

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?

It is two short clauses with no padding, and the operation is front-loaded in the German sentence before the English scope limit. The bilingual restatement is mildly redundant, but each half carries a distinct piece of information (what it does vs. what it does not do).

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-required-boolean evaluation tool with no output schema, the definition explains the inputs and the interpretive limit but never indicates what the tool returns or how the outcome is expressed. An agent knows when to call it and what to supply, but not what to expect back, which is a real 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% — all five booleans carry their own German explanations in the schema — so the schema already does the semantic work. The description only sketches the inputs at a high level ('two rain events and a dry control period') without adding interpretation beyond that. Baseline 3 is appropriate.

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 German clause names a specific operation and resource — comparing two rain events plus a dry control period in the moisture log (Feuchteprotokoll) — and the English gloss states the goal: check recurrence after rain. It is clearly distinguishable from diagnostic siblings because it explicitly disclaims defect identification. It falls short of a 5 only because no specific sibling tool is named as the 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?

The phrase 'Check recurrence after rain' sets the situation for use, and 'without identifying a building defect' supplies an explicit exclusion that steers the agent away from treating the result as a diagnosis. What is missing is a named alternative tool to route to when a defect assessment is actually wanted, which keeps this below a 5.

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