Skip to main content
Glama

getecoback-climate-weather

keller_kompressor_lueftung_getrennte_tankabnahme

Read-only

Prüfe, ob einer messbaren Tankzunahme eine zusätzliche Fensteröffnung vorausging — Mark reservoir intervals affected by a separate ventilation event

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_ab_min": "<a_ab_min>",
      "b_ab_min": "<b_ab_min>",
      "fenster_ab_min": "<fenster_ab_min>",
      "fenster_bis_min": "<fenster_bis_min>",
      "tankzuwachs_l": "<tankzuwachs_l>"
    },
    "name": "keller_kompressor_lueftung_getrennte_tankabnahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_ab_minYesZeitpunkt der ersten Tankablesung
b_ab_minYesZeitpunkt der nächsten Tankablesung ohne Leerung
tankzuwachs_lYesGemessene Zunahme zwischen beiden Ablesungen
fenster_ab_minYesBeginn einer dokumentierten Fensteröffnung
fenster_bis_minYesEnde derselben Fensteröffnung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 and data scope are covered. The description adds genuine behavioral content by disclosing the decision rule (temporal precedence of a window opening before a tank increase), but it never says what the operation returns — a boolean verdict, a set of flagged intervals, or a reclassification — which matters since no output schema exists.

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?

It is short and front-loads the core check, but the second clause is redundant and vague rather than informative, and the German/English mix costs parsing clarity without adding meaning. Roughly half of the sentences earns its place.

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?

This is a five-parameter, fully-required analytical predicate with no output schema and no annotations covering return shape. The description explains the intent but not the evaluation rule (must the window close before the second reading? what counts as 'preceding'?) or the result format, so an agent cannot reliably interpret the output.

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% and each of the five numeric parameters carries its own description, so the schema does the heavy lifting. The description only alludes to the tank delta and the window interval; it adds no rules such as required ordering (fenster_bis_min before b_ab_min), tolerance, or unit semantics beyond the schema's minutes convention.

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 concrete check — whether a measurable tank increase was preceded by an additional window opening — which names the resource (tank increase / window opening intervals) and a comparison verb. However, the two halves say different things ('Prüfe, ob ...' vs. 'Mark reservoir intervals affected by a separate ventilation event'), and the mixed German/English leaves the actual operation ('mark' vs. 'identify/flag') ambiguous. It is not clearly distinguishable from ventilation-related siblings without opening the schema.

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 when-to-use guidance, no prerequisites (e.g. that readings must come from a non-emptied reservoir, which the schema hints at), and no reference to any alternative tool for related ventilation/window questions. The agent must infer the use case purely from the tool name.

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