Skip to main content
Glama

getecoback-climate-weather

nachtwasser_ereignisse_und_restvolumen

Read-only

Wasserstandsdifferenz in einem ruhigen Fenster gegen tatsächlich protokollierte Einzelentnahmen prüfen — Reconcile known water-use events against the quiet-period meter delta.

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": {
      "fenster_l": "<fenster_l>",
      "dokumentierte_entnahmen_l": "<dokumentierte_entnahmen_l>",
      "spielraum_l": "<spielraum_l>",
      "gemeinsamer_zaehlerumfang": "<gemeinsamer_zaehlerumfang>"
    },
    "name": "nachtwasser_ereignisse_und_restvolumen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_lYesZählerdifferenz des gesamten beobachteten Fensters in Litern.
spielraum_lYesEigener begründeter kombinierter Messspielraum in Litern.
dokumentierte_entnahmen_lYesSumme der direkt gemessenen Entnahmen innerhalb desselben Fensters.
gemeinsamer_zaehlerumfangYesSind die Entnahmen diesem Zähler und demselben Zeitfenster zugeordnet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint and openWorldHint already tell the agent this is a closed, non-mutating computation. The description adds nothing about how the reconciliation behaves: no mention of how the tolerance (spielraum_l) is applied, what a mismatch implies, or what the result expresses. With no output schema, that gap is costly.

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 operation stated first and a bilingual gloss; no filler. Slight redundancy from restating the same idea in two languages, but it aids matching against German domain terms.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four required parameters and no output schema mean the description should say what the computation yields (a deviation? a pass/fail verdict?) and how the boolean scope flag changes the result. Neither is covered, so an agent cannot predict the return value or interpret an edge case.

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 the four numeric/boolean parameters are already fully documented in the schema. The description adds no format, unit, or constraint information beyond that baseline.

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 specific operation: reconciling recorded individual withdrawals against the meter delta of a quiet period. The German sentence plus English gloss makes the intent unambiguous. It does not, however, contrast itself with any sibling, several of which also deal with water/energy accounting.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The agent must infer from 'ruhiges Fenster' that this applies only to quiet-period data, with no stated preconditions (e.g. same meter, same window) beyond what the parameters imply.

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