Skip to main content
Glama

getecoback-raumklima

kuechen_spuelmittel_gesamtverbrauch_nachfuellen

Read-only

Bei protokollierter Nachfüllung den verbrauchten Teil einer vorhandenen Spülmittelpackung von einer reinen Bestandsänderung unterscheiden — Account for additions when measuring detergent stock use.

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": {
      "anfang_g": "<anfang_g>",
      "nachgefuellt_g": "<nachgefuellt_g>",
      "ende_g": "<ende_g>",
      "umgefuellt_g": "<umgefuellt_g>"
    },
    "name": "kuechen_spuelmittel_gesamtverbrauch_nachfuellen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_gYesGemessene Nettomenge am Ende in Gramm.
anfang_gYesGemessene Nettomenge im dokumentierten Behälter zu Beginn in Gramm.
umgefuellt_gYesDazwischen für andere Zwecke entnommene oder zur Aufbewahrung umgefüllte Menge in Gramm.
nachgefuellt_gYesTatsächlich hinzugefügte und separat bestätigte Menge in Gramm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The read-only, closed-world safety profile is already supplied by the annotations, and the description adds the logged-refill measurement context without contradicting it. However, it discloses neither the correction arithmetic nor the form of the result, leaving important computational behavior implicit.

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 description is compact and front-loads the applicable logged-refill scenario. The English clause is partly redundant with the German text, while the abstract phrasing could have been replaced more usefully by an explicit calculation statement.

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 four-input read-only calculation, the detailed schema and explicit scenario make the definition minimally sufficient to select and populate. With no output schema, though, the absence of a stated result, formula, and treatment of decanted or otherwise removed detergent leaves central semantics to inference.

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 baseline is 3; the description's reference to accounting for additions reinforces the role of nachgefuellt_g but adds little beyond the schema. It gives no corresponding explanation of how umgefuellt_g affects consumption or how the four measurements are combined.

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 identifies the resource and measurement goal: separating the consumed portion of an existing detergent package from a mere stock change when a refill is logged. It does not explicitly say that the tool calculates total consumption or returns a gram value, and it does not differentiate itself from any sibling by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Bei protokollierter Nachfüllung" gives a concrete trigger, while the contrast with "einer reinen Bestandsänderung" helps prevent interpreting refills as consumption. It does not expressly state when not to use the tool or name an alternative for unlogged refills or simple inventory adjustments.

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