Skip to main content
Glama

getecoback-climate-weather

geschirr_ausraeumen_restwasser_trageweg

Read-only

Zwei Ausräumrouten für beobachtete Restwassermengen in Gefäßvertiefungen vergleichen — Compare how much observed residual dish water crosses the transport route.

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": {
      "a_entlang_ml": "<a_entlang_ml>",
      "b_entlang_ml": "<b_entlang_ml>",
      "a_trocknungszeit_s": "<a_trocknungszeit_s>",
      "b_trocknungszeit_s": "<b_trocknungszeit_s>",
      "ladung_und_beobachtung_gleich": "<ladung_und_beobachtung_gleich>"
    },
    "name": "geschirr_ausraeumen_restwasser_trageweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_entlang_mlYesGemessenes Restwasser, das bei Route A aus dem Spülbereich getragen wird.
b_entlang_mlYesEntsprechendes mitgetragenes Restwasser bei Route B.
a_trocknungszeit_sYesGemessene zusätzliche Bedienzeit bei A.
b_trocknungszeit_sYesEntsprechende zusätzliche Bedienzeit bei B.
ladung_und_beobachtung_gleichYesGleiche Gefäße, beobachtete Bereiche und Wartezeit nach dem Zyklus?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read. The description adds the framing that the comparison concerns residual water crossing a transport route, but it never explains what the comparison produces (a difference, a recommendation, a verdict), which is the key behavioral fact for a computation tool.

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?

A single front-loaded sentence with the purpose stated first, then a parallel English rendering. It is appropriately sized with no filler, though the bilingual restatement is mildly redundant.

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

Completeness2/5

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

There is no output schema, so the description bears the burden of explaining the return value, yet it never says what the comparison yields. For a five-required-parameter comparison tool, this leaves the agent unable to predict the result or interpret it, a significant completeness gap.

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%, so all five parameters already carry meaning in the schema. The description adds no syntax, units, or interpretation beyond the schema's own field descriptions, so the 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 states a specific verb ('compare') and resource ('two clearing routes for observed residual water amounts in vessel recesses'), making the operation identifiable. However it does not differentiate itself from any sibling tool, leaving the agent to infer its niche without guidance.

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 implied by 'compare two routes for observed residual water,' suggesting this is a two-option comparison. But there is no explicit when-to-use/when-not-to-use guidance and no named alternatives among the many sibling tools, so selection support is limited to inference.

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