Skip to main content
Glama

getecoback-climate-weather

duschwasser_messbecher_obergrenze_fehlmengen

Read-only

Bei gesättigtem Messgefäß gemessene Teilmenge und entgangene Mengen getrennt berichten — Keep an overflowed capture as a lower bound.

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": {
      "volumen_abgelesen_l": "<volumen_abgelesen_l>",
      "uebergelaufen": "<uebergelaufen>",
      "extra_gemessen_l": "<extra_gemessen_l>",
      "extra_vollstaendig": "<extra_vollstaendig>"
    },
    "name": "duschwasser_messbecher_obergrenze_fehlmengen"
  }
}

Input Schema

NameRequiredDescriptionDefault
uebergelaufenYesGing dabei beobachtet Wasser am Messgefäß vorbei?
extra_gemessen_lYesSeparat vollständig erfasste Zusatzmenge.
extra_vollstaendigYesIst bei Überlauf die separat gemessene Aufnahmemenge nachweislich vollständig?
volumen_abgelesen_lYesErfasste Menge bis zur genutzten Ablesegrenze.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only and closed-world behavior; the description adds the key semantic behavior that overflowed captures are lower bounds and that measured and missing amounts must be reported separately. It still does not specify return structure or calculation details, but it goes beyond the annotations.

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

Conciseness5/5

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

A single compact statement with the condition front-loaded and no filler. The bilingual phrasing is slightly unusual but does not add unnecessary length.

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?

For a four-required-parameter tool with no output schema, the description does not explain the returned fields or how the missing quantities and lower bound are represented. It gives a high-level rule but leaves output interpretation to the caller.

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?

All four parameters have complete schema descriptions, so the schema carries parameter-level detail. The description only gestures at the concepts (measured subset, missed quantities, overflow) without adding formats or conditions beyond the schema fields.

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?

States a specific action: separately report the measured subset and missed quantities when the measuring vessel is saturated, and treat an overflowed capture as a lower bound. It is domain-specific and not a tautology, but it does not explicitly distinguish itself from sibling measurement tools.

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?

Gives a clear triggering condition (saturated measuring vessel / overflow) and an interpretive rule (overflowed capture as lower bound). It does not name alternatives or when not to use it, so guidance is contextual rather than exhaustive.

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