Skip to main content
Glama

getecoback-climate-weather

wassergefaess_umlauf_kennzeichen_mehrfachablesung

Read-only

Drei angezeigte Sammelmengen nur bei getrennten Umläufen als drei Beiträge zählen — Reconcile repeated reads without counting the same collected water twice.

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": {
      "a_l": "<a_l>",
      "b_l": "<b_l>",
      "c_l": "<c_l>",
      "leer_nach_a": "<leer_nach_a>",
      "leer_nach_b": "<leer_nach_b>",
      "umlaeufe_bestaetigt": "<umlaeufe_bestaetigt>"
    },
    "name": "wassergefaess_umlauf_kennzeichen_mehrfachablesung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_lYesErster kumulierter Stand.
b_lYesZweiter kumulierter Stand.
c_lYesDritter kumulierter Stand.
leer_nach_aYesVor der nächsten Ablesung nach A vollständig erfasst und geleert?
leer_nach_bYesVor der nächsten Ablesung nach B vollständig erfasst und geleert?
umlaeufe_bestaetigtYesIst für beide Übergänge belegbar, ob derselbe Sammelumlauf weiterlief?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered; the description adds the substantive decision logic that repeated reads of the same continuing circulation must not be double-counted. However, with no output schema it leaves the return shape unexplained, which is the main behavioral unknown for a pure computation tool.

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 sentences with the rule front-loaded and no filler. The German/English duplication is mildly redundant, but it widens comprehension rather than obscuring the point.

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?

Six required parameters with no output schema means the description should at least indicate the result type and how the boolean confirmations change the outcome; it gestures at the logic but never resolves what is returned. Adequate for the counting rule, thin for calling it correctly end to end.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining why the three readings (a_l/b_l/c_l) may or may not be additive and by implying that the confirmation flags (leer_nach_*, umlaeufe_bestaetigt) gate that decision. That supplies the reasoning the schema's one-line field descriptions do not.

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 description states a counting/reconciliation rule: three displayed aggregate amounts count as three contributions only when the circulations were separate. That conveys the domain intent, but it never says what the tool actually returns (a corrected total? a count? a verdict?), and the opaque name gives no independent clue. It is specific enough to distinguish from the ablation/airflow siblings, but not from a potential near-identical water-container sibling.

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?

There is no statement of when to call this versus alternatives, no prerequisite conditions, and no exclusion case. The phrase 'nur bei getrennten Umläufen' is a rule applied to the inputs rather than guidance about when the tool itself is the right choice.

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