Skip to main content
Glama

getecoback-climate-weather

saugwischer_tankstopps_planen

Read-only

Tankfüllungen oder Entleerungen aus eigenen Messwerten planen — Plan tank service stops from measured water volume and usable tank capacity.

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": {
      "role": "<role>",
      "used_l": "<used_l>",
      "capacity_l": "<capacity_l>"
    },
    "name": "saugwischer_tankstopps_planen"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesDer betrachtete Tank.
used_lYesIn einem vergleichbaren Raumdurchgang gemessener Wasserverbrauch bzw. aufgefangenes Schmutzwasser in Litern.
capacity_lYesNutzbare Tankmenge laut Anleitung oder Messung bis zur vorgesehenen Markierung.

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds that the calculation is derived purely from user-supplied measurements, but it says nothing about what a "plan" contains (number of stops, intervals, assumptions) which matters since 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?

Two short sentences, front-loaded with the action and the required inputs; no filler. The German/English duplication is slightly redundant but typical for bilingual tool surfaces and does not obscure meaning.

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 a three-parameter calculation tool with no output schema and no annotation detail beyond read-only, the description should say what the returned plan looks like (e.g. refill/empty intervals). It covers the inputs well but leaves the result underspecified.

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, including the role enum, are already documented in the schema; baseline 3 applies. The description echoes the two numeric inputs (measured volume, usable capacity) but adds no interpretation, units, or interaction rules 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 specific verb ("plan") and resource ("tank service stops"/"Tankfüllungen oder Entleerungen") and states the basis (measured water volume and usable tank capacity). It is clear on its own, but it does not distinguish itself from nearby tank-interval siblings such as entfeuchter_tank_leerintervall or befeuchter_tank_laufzeit.

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?

"From own measurements" implies the context in which this applies (when you have measured volume/capacity values), but there is no explicit when-to-use/when-not guidance and no named alternative for the other tank-planning tasks in the sibling set. Usage is only implied.

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