Skip to main content
Glama

getecoback-climate-weather

waschplatz_kurze_freigabe_nachfuellstaffel

Read-only

Zwei notwendige Befüllungen an einer nur kurz nutzbaren Wasserstelle gegen eine vorbereitete Pufferfüllung abgleichen — Use confirmed staged water to reduce work within a short refill window.

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": {
      "offen_min": "<offen_min>",
      "a_bedarf_l": "<a_bedarf_l>",
      "b_bedarf_l": "<b_bedarf_l>",
      "b_vorbereitet_l": "<b_vorbereitet_l>",
      "liter_min": "<liter_min>",
      "umsetzen_min": "<umsetzen_min>"
    },
    "name": "waschplatz_kurze_freigabe_nachfuellstaffel"
  }
}

Input Schema

NameRequiredDescriptionDefault
liter_minYesGemessene Füllrate für diese kurze Entnahme in Litern je Minute.
offen_minYesBestätigte Dauer, für die die passende Wasserstelle nutzbar ist.
a_bedarf_lYesBenötigte Wassermenge für Ziel A.
b_bedarf_lYesBenötigte Wassermenge für Ziel B.
umsetzen_minYesGemessene Zeit zum Gefäßwechsel an der Wasserstelle.
b_vorbereitet_lYesPassend vorbereitete Menge für B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds intent about reducing work in a short refill window, but it does not explain the result, edge conditions, or any behavioral constraints beyond the schema.

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 description is short and front-loads the core operation before the usage note. The bilingual phrasing is slightly redundant, but it remains efficient and readable.

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 six-required-parameter calculation with no output schema, the description does not explain what the comparison returns or how to interpret the result. Inputs are fully covered by the schema and safety is covered by annotations, but the missing return semantics leave a meaningful gap.

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%, and all six parameters are documented in the schema. The description adds the conceptual relationship between the two required fills and the prepared buffer, but it does not add syntax, units, or constraints beyond what the schema already provides.

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 states a specific action: reconciling two necessary fillings at a briefly usable water point against a prepared buffer filling. It identifies the core resources and operation, though it does not differentiate this tool from any sibling.

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?

It gives a clear usage context: use confirmed staged water to reduce work within a short refill window. It does not name alternatives or state when not to use the tool, so it stops short of full routing guidance.

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