Skip to main content
Glama

getecoback-raumklima

nachfuellstelle_quellwechsel_wegezeit_anlauf

Read-only

Eine vertraute und eine nähere Nachfüllstelle nach gemessener Startmenge und kompletter Wegzeit vergleichen — Compare water run-up and travel for two verified refill points.

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_weg_s": "<a_weg_s>",
      "b_weg_s": "<b_weg_s>",
      "a_fuell_s": "<a_fuell_s>",
      "b_fuell_s": "<b_fuell_s>",
      "a_anlauf_l": "<a_anlauf_l>",
      "b_anlauf_l": "<b_anlauf_l>",
      "ziel_und_nutzung_gleich": "<ziel_und_nutzung_gleich>"
    },
    "name": "nachfuellstelle_quellwechsel_wegezeit_anlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_weg_sYesErprobte notwendige Wegzeit über A.
b_weg_sYesWegzeit über B.
a_fuell_sYesGemessene Gesamtzeit vom Öffnen bis zur Zielmenge bei A.
b_fuell_sYesEntsprechende Gesamtzeit bei B.
a_anlauf_lYesBei A gemessene Menge vor der vorgesehenen Entnahme.
b_anlauf_lYesEntsprechende Anfangsmenge bei B.
ziel_und_nutzung_gleichYesGleicher bestätigter Zweck und gleiche benötigte Zielmenge an beiden Stellen?

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?

The annotations already establish that this is a read-only, closed-world comparison. The description adds that the comparison uses measured start quantity and complete travel time, but it does not explain what the comparison returns or how the equality condition affects 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 definition is a single, front-loaded sentence with a brief bilingual restatement. It is efficient, though the German and English halves are largely 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?

For a required-parameter computation tool with no output schema, the description does not say what result the comparison produces or how the agent should interpret it. The parameter schema is complete, but the missing output and decision semantics leave a significant contextual 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 description coverage is 100%, so the schema itself documents all seven parameters. The description only restates the high-level concepts of start quantity and travel time without adding format, threshold, or interpretation details 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 gives a specific verb and comparison subject: it compares a familiar refill point with a nearer one using measured start quantity and total travel time. It is clear what the tool does, though it does not explicitly distinguish itself from similarly named sibling tools.

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?

The phrase 'Eine vertraute und eine nähere Nachfüllstelle ... vergleichen' implies the intended use case: choosing between two refill points. However, there are no explicit when-not conditions or named alternatives, so guidance remains implicit.

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