Skip to main content
Glama

getecoback-climate-weather

wassertransport_kurven_duo_oder_einzelgefaess

Read-only

Bei zwei Engstellen prüfen, ob zwei Gefäße gemeinsam durch die gemessene Route passen — Decide whether to stage two vessels together or carry them separately.

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": {
      "gang_a_cm": "<gang_a_cm>",
      "gang_b_cm": "<gang_b_cm>",
      "einzel_cm": "<einzel_cm>",
      "duo_cm": "<duo_cm>",
      "zusatz_cm": "<zusatz_cm>",
      "kurven_erprobt": "<kurven_erprobt>"
    },
    "name": "wassertransport_kurven_duo_oder_einzelgefaess"
  }
}

Input Schema

NameRequiredDescriptionDefault
duo_cmYesGemessene Gesamtbreite beider Gefäße in der gemeinsamen Handhabung.
einzel_cmYesGrößte gemessene Breite eines Gefäßes mit der erprobten Handhabung.
gang_a_cmYesNutzbare Breite an der ersten Engstelle.
gang_b_cmYesNutzbare Breite an der zweiten Engstelle.
zusatz_cmYesVor Ort selbst gewählter zusätzlicher Platzbedarf für den Weg.
kurven_erprobtYesWurden Drehungen, Schwellen und Handhabung separat vor Ort erprobt?

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 readOnlyHint and openWorldHint annotations already establish that this is a safe, non-open-world calculation. The description adds that the tool checks route fit and decides between two handling strategies, but it does not describe the return value, how the decision is expressed, or how factors like kurven_erprobt affect the result.

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 scenario and decision. The German and English clauses convey the same content, so the bilingual duplication is slightly redundant, but it remains efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only calculation tool with six fully described required parameters and safety annotations, the description gives enough context to understand the decision being made. It could be more complete by stating the form of the result, but the core action and decision are clear.

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 documented in detail. The description mentions measured route, bottlenecks, and vessels but adds no parameter-specific meaning beyond what the schema provides, making 3 the appropriate baseline.

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 a specific check: whether two vessels fit together through a measured route with two bottlenecks, and whether to stage them together or separately. This is clear, but it does not explicitly distinguish the tool from the sibling wassertransport_relais_zwei_personen_uebergabe or other transport-related tools.

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?

The phrase 'Bei zwei Engstellen' establishes a clear usage context: use this when there are exactly two narrow points and a decision is needed between joint staging and separate carrying. It does not state when not to use the tool or name an alternative, so it falls short of explicit 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