Skip to main content
Glama

getecoback-climate-weather

luftkuehler_tankbilanz_ueber_wasserwege

Read-only

Trennt Tankabnahme, dokumentierte Verluste und die zusätzlich in der Matte verbleibende Flüssigkeit — Account for reservoir drawdown, measured losses and retained water separately.

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": {
      "start_ml": "<start_ml>",
      "nachgefuellt_ml": "<nachgefuellt_ml>",
      "ende_ml": "<ende_ml>",
      "anders_ab_ml": "<anders_ab_ml>",
      "matte_mehr_ml": "<matte_mehr_ml>",
      "wege_bilanziert": "<wege_bilanziert>"
    },
    "name": "luftkuehler_tankbilanz_ueber_wasserwege"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_mlYesGemessener Tankstand zum Ende in ml.
start_mlYesGemessener Tankstand zu Beginn in ml.
anders_ab_mlYesGetrennt belegter Flüssigkeitsabgang ohne Verdunstung in ml.
matte_mehr_mlYesGegenüber dem Start zusätzlich belegt in der Matte gebundene Menge in ml.
nachgefuellt_mlYesTatsächlich während des Blocks zugegebene Menge in ml.
wege_bilanziertYesSind Flüssigkeitswege und Messzeitpunkte einschließlich Mattenzustand vollständig belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 no behavior beyond that. It says nothing about what happens when wege_bilanziert is false, whether the computation is rejected or flagged, what unit or form the result takes, or what the tool does with inconsistent inputs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence is appropriately short and the core decomposition is front-loaded. However, the German and English halves are near-verbatim restatements, spending tokens twice on the same content without adding a usage rule, prerequisite, or result description.

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?

With six required parameters, no output schema, and no annotations describing outcome, the agent has no indication of the returned value or its meaning; the description should cover that gap and does not. For a balance-computation tool, the absence of any statement about the result or about handling of the completeness flag leaves it materially incomplete.

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 coverage is 100%, so the schema already defines all six parameters including bounds and units. The description's decomposition maps loosely onto the parameter set (drawdown, losses, mat retention), which adds a conceptual frame but no format, constraint, or interpretation details beyond the schema text.

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 names the quantities being separated (Tankabnahme, dokumentierte Verluste, in der Matte verbleibende Flüssigkeit), which conveys the subject matter, but it never states the operative result — a computed tank/water balance — nor what the tool returns. Read as a fragment ('Trennt ...'), it is understandable but leaves the agent to infer that this is a reconciliation computation rather than a measurement retrieval.

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 guidance on when to use this tool, no prerequisites, and no reference to any alternative despite many related siblings (e.g. verdunstungsgrenze, tankstand_ruecklauf_nach_stopp, vergleich_ein_tankvolumen_getrennte_laufarten). The 'wege_bilanziert' completeness flag hints at a precondition but the description never states it as one.

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