Skip to main content
Glama

getecoback-raumklima

pflege_behaelter_rest_neben_haushaltsbedarf

Read-only

Nach einer Teilrunde dokumentiert verbleibende Mengen nach ihrem vorgesehenen weiteren Weg getrennt ausweisen — Keep documented carryover separate from an unverified remainder.

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": {
      "teilmengen_und_wege_belegt": "<teilmengen_und_wege_belegt>",
      "direkt_geplant_ml": "<direkt_geplant_ml>",
      "aufheben_belegt_ml": "<aufheben_belegt_ml>",
      "offen_ml": "<offen_ml>",
      "gesamt_ml": "<gesamt_ml>",
      "messspanne_ml": "<messspanne_ml>"
    },
    "name": "pflege_behaelter_rest_neben_haushaltsbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
offen_mlYesSeparat verbliebene Menge ohne bestätigten weiteren Weg, in ml.
gesamt_mlYesUnabhängig gezählte Summe der Restmengen, in ml.
messspanne_mlYesGeschätzte gemeinsame Unsicherheit der Ablesungen, in ml.
direkt_geplant_mlYesGetrennte Menge für eine bereits bestätigte weitere Anwendung, in ml.
aufheben_belegt_mlYesWeitere Menge mit dokumentierter erlaubter Aufbewahrung, in ml.
teilmengen_und_wege_belegtYesSind die getrennten Reste in Originalgebinden gemessen und die vorgesehenen Wege belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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. The description adds the domain invariant that verified carryover must be kept separate from an unverified remainder, which is genuine behavioral content. However, it never says what the tool returns or what happens when gesamt_ml disagrees with the sum of the three partial quantities, which matters for a pure read-only tool with 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.

Conciseness3/5

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

The content is short and front-loaded with the trigger condition, but the German sentence is immediately restated in English as a paraphrase rather than a translation, duplicating the same idea without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Six required numeric parameters, a consistency relationship between the total and its parts, and no output schema make this a non-trivial tool, yet the description supplies only one abstract sentence about separation. For a read-only tool an agent still cannot tell whether it validates, computes, or merely echoes the inputs.

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 all six parameters carry their own German descriptions with units and ranges, so the baseline is 3. The phrase 'nach ihrem vorgesehenen weiteren Weg getrennt' loosely maps to the three quantity buckets (directly planned, documented storage, open), but adds no rule about how gesamt_ml and messspanne_ml relate to those buckets.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an operation (reporting remaining quantities separated by intended further path after a partial round) but stays abstract and jargon-heavy, without a concrete verb-object an agent can anchor on. It gives no signal distinguishing it from close siblings such as pflegegruppe_ein_teil_bearbeitet_rest_nachhalten or pflege_teilrunde_arbeitsmittel_als_gruppe_zurueck.

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 only usage context is the temporal trigger 'Nach einer Teilrunde', which is implied rather than stated as a when-to-use rule. There is no statement of when not to use it and no named alternative among the many similarly named sibling tools.

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