Skip to main content
Glama

getecoback-climate-weather

wassertransport_relais_zwei_personen_uebergabe

Read-only

Übergabe eines vorgesehenen Wassergefäßes zwischen zwei Personen mit beider Zeitfenstern prüfen — Fit a measured two-person handoff to both schedules.

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": {
      "ankunft_a": "<ankunft_a>",
      "a_bis": "<a_bis>",
      "b_ab": "<b_ab>",
      "b_bis": "<b_bis>",
      "uebergabe_min": "<uebergabe_min>",
      "uebergabeort_geprueft": "<uebergabeort_geprueft>"
    },
    "name": "wassertransport_relais_zwei_personen_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
b_abYesFrühestes Eintreffen von Person B.
a_bisYesBis wann Person A am selben Tag am Ort bleiben kann.
b_bisYesSpätester Aufbruch von Person B.
ankunft_aYesBeobachtet erreichbare Ankunft am vereinbarten Übergabeort.
uebergabe_minYesVor Ort beobachtete Dauer der Übergabe einschließlich Abstellen.
uebergabeort_geprueftYesSind der Ort, geeignete Gefäße und die Handhabung bei der tatsächlichen Füllung bestätigt?

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?

The 'prüfen' framing is consistent with readOnlyHint=true and openWorldHint=false, and 'Fit a measured two-person handoff' hints that the computation is deterministic and based on observed values. Beyond that the description adds little: it does not say what a failed fit means, whether the caller should retry with different inputs, or what the verdict looks like. With annotations already covering the safety profile, this is adequate but thin.

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?

Two clauses, front-loaded with the German purpose before the English restatement; nothing superfluous. The German and English halves are near-duplicates, which costs a little space but keeps intent unambiguous across languages.

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?

Six required parameters are fully documented in the schema and the description correctly frames the tool as a two-window fit check. However, for a pure validation tool with no output schema, the description should state what the result is (feasible vs. infeasible, and whether remedies are suggested); that information is absent.

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 coverage is 100% and each of the six fields carries a precise German description, so the schema does the heavy lifting. The description reinforces that the two window pairs belong to two distinct persons and that the handoff duration is 'measured' (matching uebergabe_min's observed-duration semantics), but adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 concrete verb and resource: checking ('prüfen') whether a designated water vessel handoff ('Übergabe eines vorgesehenen Wassergefäßes') fits between two people's time windows. That is specific enough that an agent knows it is a feasibility check rather than a transport planner. It does not differentiate itself from the many other two-person scheduling/validation siblings in the catalog.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative among the numerous zwei_personen siblings. The only implicit signal is the verb 'prüfen', which suggests a validation call rather than a planning call, but the description never states to which situations that applies.

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