Skip to main content
Glama

getecoback-climate-weather

saugwischer_mittelmenge

Read-only

Freigegebene manuelle Dosierangabe auf die verwendete Wassermenge umrechnen — Scale an approved manual dilution to the actual tank fill.

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": {
      "dose_ml_per_l": "<dose_ml_per_l>",
      "water_l": "<water_l>",
      "approved_manual_dose": "<approved_manual_dose>"
    },
    "name": "saugwischer_mittelmenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
water_lYesTatsächlich eingefüllte Wassermenge in Litern.
dose_ml_per_lYesAusdrücklich dokumentierte Milliliter Konzentrat pro Liter Wasser.
approved_manual_doseYesMittel, Boden, manuelle Dosierung und die Angabe pro Liter Wasser sind eindeutig freigegeben?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description reinforces this by framing the operation as a pure recalculation, but it never says what is produced (presumably milliliters of concentrate), what happens if approved_manual_dose is false, or how rounding/limits are handled — notable because there is no output schema.

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 that wastes no words, with the gating concept ('Freigegebene') placed first. The bilingual duplication restates the same content in English, which is mildly redundant but defensible for a German-domain tool.

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 only three fully documented parameters the input side is adequately covered, but for a calculation tool with no output schema the description should describe the returned quantity and units. As written, an agent knows what to supply but not what it will receive back.

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 all three parameters are already fully documented in the input schema, establishing a baseline of 3. The description's phrasing ('approved manual dilution', 'actual tank fill') maps loosely onto the parameters but adds no constraints or interpretation beyond what the schema already states.

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?

States a specific verb+resource pair: converting ('umrechnen'/'scale') an approved manual dilution ratio onto the actual tank fill volume. An agent can tell this is a computation/derivation tool, not a lookup or mutation. It does not, however, distinguish itself from adjacent domain tools such as saugwischer_reinigungsmittel_freigabe or saugwischer_wasserbilanz, so it falls short of a 5.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, and names no alternative tool. The only routing signal — that the manual dose must be 'freigegeben' (approved) — is embedded in the approval parameter rather than stated as a precondition in the description.

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