Skip to main content
Glama

getecoback-raumklima

luftkuehler_vergleich_ein_tankvolumen_getrennte_laufarten

Read-only

Prüft ob eine Tanklaufzeitangabe aus dem gesuchten Nassbetrieb oder nur aus einer anderen Nutzung stammt — Verify whether a published tank runtime refers to the intended wet-use setup.

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": {
      "betriebsart": "<betriebsart>",
      "nutzvolumen_belegt": "<nutzvolumen_belegt>",
      "luftstufe_belegt": "<luftstufe_belegt>",
      "lokaler_nutzen_belegt": "<lokaler_nutzen_belegt>"
    },
    "name": "luftkuehler_vergleich_ein_tankvolumen_getrennte_laufarten"
  }
}

Input Schema

NameRequiredDescriptionDefault
betriebsartYesBetriebsart hinter der Angabe.
luftstufe_belegtYesDie für den Vergleich benötigte beobachtete Luftstufe ist angegeben.
nutzvolumen_belegtYesDie Messung ist dem nutzbaren Volumen desselben Tanks zugeordnet.
lokaler_nutzen_belegtYesDie Angaben belegen auch eine Messung am eigenen Nutzplatz.

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 safety is covered. The description adds the substantive purpose (separating wet-use runtimes from other-use runtimes), but says nothing about what the tool produces or how the four supplied flags are weighed into a verdict, and no output schema exists to fill that gap.

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, front-loaded clauses with the verification target stated first and the criterion second. The German/English mirroring is redundant but standard for bilingual definitions and costs little; no filler beyond that.

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?

For a tool with four required boolean evidence flags and no output schema, the description should indicate what a positive versus negative determination looks like and what happens when evidence flags are false. It stops at the question being asked, leaving the result semantics and the pass/fail logic undocumented.

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 every parameter including the 'betriebsart' enum is already documented in structured form. The description touches the semantics by naming 'Nassbetrieb' (matching the 'nass' enum value) and 'andere Nutzung', but adds no rules about how 'nutzvolumen_belegt', 'luftstufe_belegt' and 'lokaler_nutzen_belegt' interact or what combinations invalidate a claim.

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 verification action ('Prüft ob / Verify whether') applied to a specific artifact ('Tanklaufzeitangabe / published tank runtime'), and clarifies the ambiguity being resolved: wet-use setup versus another use. This is meaningfully more precise than the cryptic tool name, though it never explains the 'ein Tankvolumen' / 'getrennte Laufarten' framing that the name promises.

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 intent implies when the check is relevant (validating a claimed tank runtime before relying on it), but there is no explicit when-to-use, when-not-to-use, or routing to any of the many luftkuehler_* siblings that cover adjacent evidence questions. The agent must infer the trigger condition.

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