Skip to main content
Glama

getecoback-climate-weather

saugwischer_fuellstelle_vor_abschnitt

Read-only

Zwei Reinigungsabschnitte mit eigenem gemessenem Verbrauch und einer erlaubten Nachfüllstelle abgleichen. — Check whether the next approved refill point arrives before either cleaning segment runs short.

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": {
      "start_ml": "<start_ml>",
      "a_bedarf_ml": "<a_bedarf_ml>",
      "b_bedarf_ml": "<b_bedarf_ml>",
      "nachfuellen_ml": "<nachfuellen_ml>",
      "tank_max_ml": "<tank_max_ml>"
    },
    "name": "saugwischer_fuellstelle_vor_abschnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_mlYesTatsächlich eingefüllte nutzbare Menge beim Start in Millilitern.
a_bedarf_mlYesAuf ähnlicher freigegebener Fläche gemessener Bedarf für Abschnitt A.
b_bedarf_mlYesGemessener Bedarf für Abschnitt B mit derselben Einstellung.
tank_max_mlYesPraktisch nutzbare Tankfüllung laut Anleitung in Millilitern.
nachfuellen_mlYesZwischen beiden Abschnitten an der vorgesehenen Stelle verfügbare, zugelassene Nachfüllmenge.

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 already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description is consistent with it. The description adds that the tool performs a comparison of measured consumption against a permitted refill quantity, which frames it as an analytical check rather than a mutation. It does not disclose what the outcome looks like or how borderline cases (e.g., refill exactly at the shortfall) are treated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The statement is short and front-loaded, but it is delivered twice, once in German and once in English, with only marginal added information in the second version. The bilingual duplication consumes space without adding decision-relevant detail, though nothing is actively misleading.

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?

With five required numeric parameters, no output schema, and read-only annotations, the definition is adequate but leaves a real gap: it never says what the tool returns (a verdict, a margin in milliliters, per-segment shortfall). For a decision-support tool with no output schema, that missing piece matters. The input side is otherwise fully described via the schema.

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%, and every parameter carries a units-and-meaning description, so the schema does the heavy lifting. The description reinforces the roles of the five inputs (two segments' consumption, start amount, refill allowance, tank maximum) but adds no new syntax, units, or constraint guidance 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 operation: reconciling two cleaning segments, each with its own measured consumption, against one permitted refill point, and checking whether the refill arrives before either segment runs short. This is a specific verb-plus-resource statement an agent can act on. It stops short of distinguishing itself from the many similarly named saugwischer_* siblings, so it is clear but not differentiated.

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 'Check whether...' clause implies the usage context (a pre-run feasibility check on refill timing), but there is no explicit statement of when to use this versus alternatives such as saugwischer_geteilte_pflege_letzte_tankphase or saugwischer_mittelmenge. No exclusions or preconditions are given, so the agent must infer the fit from the name and phrasing.

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