Skip to main content
Glama

getecoback-raumklima

armatur_tropfverlust_schaetzen

Read-only

Eine aufgefangene Tropfmenge auf einen begrenzten Zeitraum hochrechnen — Project a captured drip rate over a limited observation period.

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": {
      "aufgefangen_ml": "<aufgefangen_ml>",
      "messdauer_min": "<messdauer_min>",
      "tage": "<tage>"
    },
    "name": "armatur_tropfverlust_schaetzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
tageYesVergleichbare Tage bei angenommener unveränderter Tropfrate.
messdauer_minYesDauer der Beobachtung in Minuten.
aufgefangen_mlYesAufgefangene Wassermenge in Millilitern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare a read-only, closed-world calculation. The description adds that it projects a captured drip amount over a limited period, but does not state output units, the constant-rate assumption, precision, or other calculation behavior beyond what annotations and schema provide.

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?

The purpose is front-loaded, but the same sentence is provided in both German and English, duplicating content rather than adding structure or value. It is short, but the repetition weakens conciseness.

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 simple read-only estimator with three fully documented inputs, the schema carries most of the needed detail. However, no output schema exists and the description does not explain what result is returned, such as ml per day or total ml over the chosen days, nor does it state key assumptions.

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%, and all three inputs are fully described with ranges and meanings. The description only restates captured drip amount and observation period, adding no units, constraints, or interpretation beyond the schema, so the baseline 3 is appropriate.

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 verb and resource: projecting a captured drip amount over a limited observation period. An agent can tell it is an extrapolation/estimation tool, but the description does not distinguish it from any sibling alternative, so it is clear but not fully differentiated.

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 captured-drip scenario implies when the tool is useful, but there is no explicit when-to-use guidance, no exclusions, and no named alternative for related measurement or estimation tasks. Usage is therefore inferable but not spelled out.

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