Skip to main content
Glama

getecoback-raumklima

wasserkocher_fuellsplitt_mindestmenge

Read-only

Schon bekannten Wasserbedarf auf erlaubte Kannenfüllungen verteilen — Schedule equal kettle batches within the documented minimum and maximum.

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": {
      "bedarf_ml": "<bedarf_ml>",
      "min_ml": "<min_ml>",
      "max_ml": "<max_ml>"
    },
    "name": "wasserkocher_fuellsplitt_mindestmenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_mlYesHöchstfüllung laut Anleitung.
min_mlYesMindestfüllung laut Anleitung.
bedarf_mlYesBenötigte Gesamtmenge in Millilitern.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a pure, closed-world computation. The description adds genuine behavioral detail by specifying that batches are EQUAL and must respect documented min/max bounds. It does not disclose edge-case behavior (e.g., what happens when bedarf_ml is not evenly divisible or falls outside min/max), and with no output schema the return shape is left unexplained.

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 clauses, front-loaded with the core operation and the equal-batch constraint, with no filler. The German and English sentences are near-duplicates, which costs a little density but reasonably serves as a translation gloss.

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 computation tool with no output schema, the description covers the input intent but says nothing about what is returned (batch sizes, batch count, or how remainders are handled). Given that the output contract is entirely absent from structured data, this is a meaningful gap rather than a minor one.

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% with per-property descriptions and 0-5000 bounds, so the schema already carries the parameter burden and baseline 3 applies. The description only loosely reinforces the mapping (bedarf as the total, min/max as documented fill limits) without adding format, rounding, or divisibility semantics.

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 concrete operation: distribute an already-known total water requirement (bedarf_ml) across permitted kettle fill levels, producing equal batches bounded by the documented minimum and maximum. That is a specific verb+resource combination an agent can recognize. It does not distinguish itself from near siblings such as wasserkocher_mehrmenge_szenario or wasserkocher_wahlstufe_abgleichen, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Schon bekannten Wasserbedarf" implies the precondition that the total demand is already established, which is useful context for selecting this tool. However, there is no explicit when-to-use/when-not guidance and no named alternative for the case where the demand is not yet known or where the split must vary by batch. 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