Skip to main content
Glama

getecoback-climate-weather

luftkuehler_tankstand_ruecklauf_nach_stopp

Read-only

Prüft wie viel der Abnahme im laufenden Betrieb nach dokumentiertem Stopp wieder im selben Tank sichtbar wurde — Quantify the observed return to the reservoir after normal stop.

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": {
      "vor_run_ml": "<vor_run_ml>",
      "beim_stopp_ml": "<beim_stopp_ml>",
      "nach_restzeit_ml": "<nach_restzeit_ml>",
      "nur_ruecklauf": "<nur_ruecklauf>"
    },
    "name": "luftkuehler_tankstand_ruecklauf_nach_stopp"
  }
}

Input Schema

NameRequiredDescriptionDefault
vor_run_mlYesTankstand vor Laufbeginn in ml.
beim_stopp_mlYesTankstand beim dokumentierten Stopp in ml.
nur_ruecklaufYesDerselbe ruhende Tank und keine Nachfüllung, Entnahme oder andere bekannte Veränderung?
nach_restzeit_mlYesSpäter im selben Tank abgelesener Wert in ml.

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 agent knows this is a closed-world computation with no side effects. The description adds that this is an observational quantification, but it does not say what is computed (absolute ml, delta, ratio?), what happens if nur_ruecklauf is false, or whether implausible level readings are rejected. Useful context beyond the annotations, but thin for a calculation tool with 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 short sentences with the measurement condition front-loaded. The English half is a near-verbatim restatement of the German half, which adds redundancy but also disambiguates the terse German phrasing, so the cost is small.

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?

All four required parameters are documented and the safety profile is covered by annotations, so the agent can call it. However, with no output schema the description should state the shape of the result (delta in ml vs. percentage) and the precondition that the stop be documented; that omission leaves a real gap for a pure computation tool.

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%, with each of the four parameters (vor_run_ml, beim_stopp_ml, nach_restzeit_ml, nur_ruecklauf) explicitly documented in the schema, so the baseline is 3. The description does not explain how the three level readings are combined into the 'return' figure, which is the one piece of semantics the schema cannot supply.

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 states a specific operation: quantifying how much of the draw-down reappears in the same tank after a documented stop ('Quantify the observed return to the reservoir after normal stop'). The verb+resource is identifiable, though it never names which sibling tank-balance tool (e.g. luftkuehler_tankbilanz_ueber_wasserwege, luftkuehler_wasserverlust_stillstand_kontrolllauf) it is the alternative to, so the agent must infer differentiation.

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 trigger condition is embedded rather than stated: 'nach dokumentiertem Stopp' and 'im laufenden Betrieb' imply when the measurement applies. There is no explicit when-not guidance, no prerequisite that a stop must be documented first, and no routing to competing tank-level siblings. Usage is implied, not prescribed.

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