Skip to main content
Glama

getecoback-raumklima

fensterbank_tropfen_nachlauf_messgrenze

Read-only

Nach einer Fensterreinigung frühe und späte Tropfenmengen anhand zweier gelesener Sammelstände trennen — Split measured late drips from the initial collection.

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": {
      "erster_stand_ml": "<erster_stand_ml>",
      "spaeter_stand_ml": "<spaeter_stand_ml>",
      "abstand_min": "<abstand_min>",
      "behoelter_unveraendert": "<behoelter_unveraendert>"
    },
    "name": "fensterbank_tropfen_nachlauf_messgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
abstand_minYesBeobachtete Minuten zwischen den Ständen.
erster_stand_mlYesFrüher Stand des geleerten und danach verwendeten Sammelbehälters.
spaeter_stand_mlYesSpäter kumulierter Stand desselben Behälters.
behoelter_unveraendertYesWar der Behälter am selben Ort und blieb er ungeleert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 nothing beyond that: no note on how the two readings are combined, no caveat about the required 'behoelter_unveraendert' gate, no mention of units or invalid-input handling.

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, but the value is diluted by a redundant German-English duplication of the same idea and several spelling errors that make the single sentence harder to parse. Front-loading the core action is fine; the rest does not earn its space.

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 computation with no output schema, the definition should explain what result is produced (e.g., a separated late-drip quantity) and what happens when 'behoelter_unveraendert' is false. Neither is present, leaving the agent to infer the tool's contract.

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 carry schema descriptions (100% coverage), including units (ml, minutes) and the meaning of the unchanged-container flag. The description adds no interpretation of these parameters, so the schema does all the work and the baseline 3 applies.

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 names an operation (splitting early vs. late drip volumes from two readings) but is worded vaguely and in a typo-ridden mix of German and English, so the exact computation and its result are not stated. An agent can guess the domain but cannot state precisely what the tool returns or how it differs from the many *nachlauf* siblings.

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?

No when-to-use guidance, no preconditions, and no routing to or away from alternatives. The sibling list contains numerous closely named *nachlauf* / *messgrenze* tools, yet the definition gives no criterion for choosing this one.

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