Skip to main content
Glama

getecoback-climate-weather

gefaess_umfuellen_zwischenrest_ruecklauf

Read-only

Transportrest beim Zwischengefäß von bewusst zurückgebrachtem Volumen trennen — Account for heel volume separately from liquid carried back.

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": {
      "start_l": "<start_l>",
      "ziel_l": "<ziel_l>",
      "ruecklauf_l": "<ruecklauf_l>",
      "bodensatz_l": "<bodensatz_l>"
    },
    "name": "gefaess_umfuellen_zwischenrest_ruecklauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_lYesAm Ziel tatsächlich abgegebene Menge.
start_lYesAm Start in das Transportgefäß gefüllte Menge.
bodensatz_lYesSeparat gemessener Rest im Transportgefäß nach der Rückgabe.
ruecklauf_lYesTatsächlich in den Startbehälter zurückgegebener Rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety behavior is covered. The description adds domain context about separating heel volume from returned liquid, but does not explain the calculation, result shape, or handling of inputs 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 definition is two compact clauses with no filler, and the core distinction is front-loaded. The bilingual phrasing is slightly redundant but not harmful.

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 read-only tool with four fully documented required parameters and no output schema, the description gives enough conceptual context to understand the domain distinction. However, it never explains what the tool returns, which is a meaningful gap when no output schema exists.

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 four parameters are already documented in detail. The description reinforces the conceptual split between residue and returned volume but adds no syntax, units, or parameter-specific meaning beyond the schema.

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 names the specific operation — separating heel/transport residue at the intermediate vessel from deliberately returned volume — and reinforces it with an English gloss. It is clear enough to identify the tool's job, though it does not explain what is produced or how the separation is computed.

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, prerequisites, or comparison to alternatives is provided. The only implied context is accounting for heel volume separately, which is thin.

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