Skip to main content
Glama

getecoback-raumklima

kondensat_messgrenze_geteilte_auffangstelle

Read-only

Eine gemeinsam benutzte Auffangstelle nur mit getrennten Proben als Gerätemessung verwenden — Separate attributable collections from mixed collection volumes.

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": {
      "einzeln_a_l": "<einzeln_a_l>",
      "einzeln_b_l": "<einzeln_b_l>",
      "gemeinsam_l": "<gemeinsam_l>",
      "sammelwege_voll_erfasst": "<sammelwege_voll_erfasst>"
    },
    "name": "kondensat_messgrenze_geteilte_auffangstelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
einzeln_a_lYesSeparat beobachtete Wassermenge mit nur Gerät A.
einzeln_b_lYesSeparat beobachtete Wassermenge mit nur Gerät B.
gemeinsam_lYesGemessenes Sammelwasser während beider dokumentierten Nutzungen.
sammelwege_voll_erfasstYesSind die drei Abschnitte vollständig und ohne Übertrag aus einem vorherigen Behälter?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety profile is covered. The description adds the separate-samples constraint, but it does not explain what the tool calculates or returns, nor how mixed volumes are handled.

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?

The definition is a single compact sentence with the usage constraint front-loaded. The bilingual German/English phrasing is somewhat redundant, but there is no unnecessary padding.

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 four-parameter required-input tool with no output schema, so the description should explain more about the operation and result. It gives only a cryptic usage condition and does not make clear what the tool does with the measurements.

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%, so all four parameters are already documented in the input schema. The description reinforces the distinction between separate and mixed collection volumes but adds no parameter-specific semantics beyond that.

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 hints at separating attributable collections from mixed collection volumes, but it does not clearly state the operation the tool performs. It is more a usage constraint than a crisp verb-plus-resource definition, leaving the exact purpose vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'nur mit getrennten Proben als Gerätemessung verwenden' gives an explicit condition for use and implies mixed collection volumes are not appropriate. It does not name an alternative sibling tool, but the when-to-use context is clear.

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