Skip to main content
Glama

getecoback-climate-weather

wandfeuchte_beobachtung_dokumentieren

Read-only

Mess- und Ereignisprotokoll für auffällige Feuchte an einer Wand zusammenstellen — Identify missing chronology and observations for a damp-wall assessment.

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": {
      "ort_und_verlauf_dokumentiert": "<ort_und_verlauf_dokumentiert>",
      "klima_protokolliert": "<klima_protokolliert>",
      "regen_oder_leitungsereignis": "<regen_oder_leitungsereignis>",
      "wiederkehrend": "<wiederkehrend>"
    },
    "name": "wandfeuchte_beobachtung_dokumentieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
wiederkehrendYesDie Stelle tritt wiederholt auf, bleibt nass oder es zeigt sich sichtbarer Befall?
klima_protokolliertYesRaumtemperatur, Luftfeuchte und Lüftungsereignisse im selben Zeitraum notiert?
regen_oder_leitungsereignisYesVerdacht auf Zusammenhang mit Regen, Leck oder anderem Wassereintritt?
ort_und_verlauf_dokumentiertYesDatum, betroffene Stelle und Veränderung der Fläche dokumentiert? Keine Adresse eingeben.

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?

The readOnlyHint/openWorldHint annotations already establish that this is a safe, closed-world evaluation with no external calls. The description adds real value by stating the tool's function is to surface *missing* chronology and observations rather than merely store inputs, but it does not say what the response contains (a gap list? a structured protocol?) despite having no output schema.

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 compact clauses with no filler, and the resource is front-loaded. The mixed German/English second clause restates the first rather than adding new information, which is a minor redundancy but not harmful.

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 four-required-boolean, read-only assessment tool with full schema coverage, the description covers what inputs represent and that gaps are the point. It is incomplete only in not hinting what the agent receives back, which matters because 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% — each of the four booleans carries its own clarifying question (recurrence, climate logging, rain/pipe event, location and progression documented, with an explicit 'no address' instruction). The description adds no meaning beyond these, so the 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?

Names a concrete resource (Mess- und Ereignisprotokoll für Feuchte an einer Wand) and a concrete action (zusammenstellen / identify missing chronology and observations). An agent can tell this is a damp-wall documentation/gap-assessment tool. It is slightly muddy whether the tool assembles a protocol or audits an existing one, but the resource is clearly distinguishable from the sibling tools.

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?

The phrase 'for a damp-wall assessment' implies the situation in which to use it, and the parameters make the intended intake scenario obvious. However, there is no explicit when-to-use vs when-not guidance and no reference to related documentation tools (e.g. fensterrahmen_entwaesserung_dokumentieren or bad_feuchte_erholung_protokoll), so routing must be inferred from the name alone.

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