Skip to main content
Glama

getecoback-climate-weather

gefaess_refill_zwei_abnehmer_verlustreserve

Read-only

Zwei belegte Füllmengen an Zielorten aus dem Vorrat nach eigenen Umfüllverlusten reservieren — Reserve source volume for two measured transfer routes.

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": {
      "bereit_l": "<bereit_l>",
      "ziel_a_l": "<ziel_a_l>",
      "ziel_b_l": "<ziel_b_l>",
      "verlust_a_l": "<verlust_a_l>",
      "verlust_b_l": "<verlust_b_l>",
      "routen_erprobt": "<routen_erprobt>"
    },
    "name": "gefaess_refill_zwei_abnehmer_verlustreserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
bereit_lYesVerfügbarer gemessener Startbestand.
ziel_a_lYesAm ersten Ziel benötigte ankommende Menge.
ziel_b_lYesAm zweiten Ziel benötigte ankommende Menge.
verlust_a_lYesZusätzlich im erprobten Gefäß und beim Umfüllen zu Ziel A verbleibende Menge.
verlust_b_lYesEntsprechende Menge für Ziel B.
routen_erprobtYesSind beide Verlustmengen auf der vorgesehenen Route erprobt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false. The description adds useful context that the reservation is loss-adjusted for two transfer routes, but it does not clarify whether the tool merely checks feasibility or returns a reservation amount, nor what happens if stock is insufficient.

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 core operation front-loaded. The bilingual restatement is somewhat redundant, but it remains short 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?

The input side is complete because every required parameter has a schema description. However, there is no output schema and the description does not explain the return value, insufficient-stock behavior, or how the routen_erprobt flag affects the result, leaving a meaningful gap for a six-parameter tool.

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 six parameters are already well documented in the schema. The description reinforces the two destinations and loss handling but adds no units, constraints, or relational semantics beyond what the schema 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 verb and resource: reserve source volume for two measured transfer routes after transfer losses. It is clear what the tool does, but it does not distinguish itself from the many sibling tools that also handle two quantities or two destinations.

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 scenario is implied: use this when two destination amounts are known and transfer losses must be accounted for. There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance, so an agent must infer the fit from the scenario.

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