Skip to main content
Glama

getecoback-raumklima

wassertragen_mehrweg_kleine_fuellungen_zeit

Read-only

Zwei vor Ort geprüfte Tragewege mit verschieden großen Füllungen nach erledigten Gängen vergleichen — Compare trips and time with route-specific carried volumes.

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": {
      "aufgabe_l": "<aufgabe_l>",
      "a_pro_gang_l": "<a_pro_gang_l>",
      "b_pro_gang_l": "<b_pro_gang_l>",
      "a_umlauf_s": "<a_umlauf_s>",
      "b_umlauf_s": "<b_umlauf_s>",
      "a_letzter_s": "<a_letzter_s>",
      "b_letzter_s": "<b_letzter_s>",
      "wege_geprueft": "<wege_geprueft>"
    },
    "name": "wassertragen_mehrweg_kleine_fuellungen_zeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgabe_lYesInsgesamt zu transportierende Menge ohne Zusatzaufgabe am Ziel.
a_umlauf_sYesGemessene Dauer von Füllen, Tragen, Abgeben und Rückweg bei A.
b_umlauf_sYesGemessene Dauer eines vollständigen Umlaufs bei B.
a_letzter_sYesGemessene Dauer des letzten Gangs ohne Rückweg bei A.
b_letzter_sYesEntsprechende Dauer bei B.
a_pro_gang_lYesErprobte Füllmenge je Gang über A in Litern.
b_pro_gang_lYesErprobte Füllmenge je Gang über B in Litern.
wege_geprueftYesSind beide Wege und die Handhabung mit der jeweiligen Füllung 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?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world computation. The description adds that inputs must be empirically verified on-site, which is genuine behavioral context, but it says nothing about what the comparison produces (trip counts, time delta, recommendation) or how ties/invalid inputs are handled.

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 short clauses, front-loaded with the core comparison, with zero padding or marketing language. The bilingual restatement is mildly redundant but does clarify the German terminology for an agent, so it largely earns its place.

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 and eight-required-parameter computation tool with no output schema, the definition should say what the caller receives back; it does not. The input side is fully covered by the schema and the verification precondition is at least hinted at, so the remaining gap is the result shape and interpretation.

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 the schema already explains each of the eight measurements, including the last-trip-without-return distinction. The description only frames them collectively as 'route-specific carried volumes' and 'erledigte Gänge', adding framing but no syntax, unit or edge-case 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 a concrete action (compare two verified carrying routes with different fill volumes) and the quantity computed (trips and time). It is specific enough to distinguish from a generic water-budget calculator, but it never names or contrasts a sibling, and the German/English restatement partly repeats rather than sharpens the purpose.

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?

Usage is only implied: 'nach erledigten Gängen' and 'vor Ort geprüfte' suggest the routes must already be measured before calling, and the required boolean wege_geprueft encodes that precondition. There is no explicit when-to-use vs. when-not guidance, no statement of what happens if the routes are unverified, and no pointer to an alternative tool for single-route estimates.

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