Skip to main content
Glama

getecoback-climate-weather

wasserverlauf_verzoegerte_anlage_ereignisvolumen

Read-only

Nach dokumentierter Nutzung eine einmalige spätere automatische Wasserentnahme im Beobachtungsfenster erfassen — Attribute a delayed but confirmed water event to the logged task without moving the meter timestamp.

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": {
      "nutzung_l": "<nutzung_l>",
      "nachlauf_fenster_l": "<nachlauf_fenster_l>",
      "bestaetigt_nachlauf_l": "<bestaetigt_nachlauf_l>",
      "nachlauf_zuordnung": "<nachlauf_zuordnung>"
    },
    "name": "wasserverlauf_verzoegerte_anlage_ereignisvolumen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nutzung_lYesGemessene Wasserentnahme während einer abgeschlossenen Haushaltsaufgabe.
nachlauf_fenster_lYesGemessene Wasserentnahme eines separat abgegrenzten späteren Fensters.
nachlauf_zuordnungYesSind Zeitstempel, Gerätedokumentation und Volumen der späteren Entnahme nachvollziehbar zugeordnet?
bestaetigt_nachlauf_lYesDavon nachweislich als zur Aufgabe gehörende spätere automatische Entnahme gemessen.

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 the safety profile is largely covered. The description adds useful behavioral context: the event is 'einmalig' (one-off), it is confined to the observation window, and the meter timestamp is explicitly left untouched. It does not say whether the attribution is persisted anywhere or what the tool returns, and the verb 'erfassen' sits slightly in tension with a pure read, though 'ohne den Zählerzeitstempel zu verschieben' keeps it consistent enough not to be a contradiction.

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?

A single, front-loaded sentence with the precondition first and the key non-effect ('without moving the meter timestamp') last. The German and English halves restate each other, which aids bilingual readers but is mild duplication rather than bloat.

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 four-required-parameter classification/attribution call with full schema coverage and read-only annotations, so most structured burden is carried elsewhere. What is missing is any hint of the outcome — for a tool with no output schema, the description should indicate what an agent gets back (e.g. an attributed volume or a validity verdict) before it can judge whether the call succeeded.

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 four parameters (measured consumption, later-window volume, plausibility flag, confirmed delayed volume) are already documented in the schema. The description adds only the framing idea of confirming a delayed event against a logged task; it does not explain how nachlauf_fenster_l relates to bestaetigt_nachlauf_l or when nachlauf_zuordnung should be false. 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 names a concrete action on a concrete object: record/attribute a one-off, later, automatic water withdrawal that falls inside the observation window to the already logged task. The clause 'without moving the meter timestamp' sharpens the scope against other wasserverlauf tools, giving an agent enough to tell it apart from a plain meter-reading tool, though no sibling is named outright.

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 opening 'Nach dokumentierter Nutzung' establishes a precondition (a household task must already be logged), which implies when to use it. However, there is no explicit when-not guidance, no mention of the sibling tools that handle first-flush or double-occupancy volumes, and no statement about what to do if the later withdrawal is not confirmed.

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