Skip to main content
Glama

getecoback-climate-weather

verbrauchsmittel_zwei_originalbehaelter_einzelbedarf

Read-only

Zwei Originalgebinde nach bestätigter Nutzungsfrist für ganze Anwendungen einplanen — Allocate whole uses from two original containers without combining remnants.

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": {
      "vorgaben_bestaetigt": "<vorgaben_bestaetigt>",
      "a_ml": "<a_ml>",
      "b_ml": "<b_ml>",
      "a_bis": "<a_bis>",
      "b_bis": "<b_bis>",
      "termin": "<termin>",
      "je_arbeit_ml": "<je_arbeit_ml>",
      "bedarf": "<bedarf>"
    },
    "name": "verbrauchsmittel_zwei_originalbehaelter_einzelbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_mlYesNutzbare Restmenge in Originalgebinde A.
b_mlYesNutzbare Restmenge in Originalgebinde B.
a_bisYesLetzter belegter Nutzungstag für A.
b_bisYesLetzter belegter Nutzungstag für B.
bedarfYesAnzahl ganzer Anwendungen am Termin.
terminYesTag der geplanten Anwendungen.
je_arbeit_mlYesBereits belegte Menge je Anwendung.
vorgaben_bestaetigtYesSind beide Gebinde exakt passend und sind Fristen und Mengen für diese Anwendungen belegt?

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 safety is covered and only incremental context is needed. The description adds a real behavioral rule — that allocations must come from whole uses of each container and remnants may not be pooled — which is not carried by the annotations. It does not say what the tool returns or how an infeasible combination is reported, which matters for an 8-parameter feasibility computation 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.

Conciseness4/5

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

Two short sentences, front-loaded with the core allocation rule and its key constraint. The second sentence is a straight English rendering of the first and contributes no new information, which is the only waste; otherwise there is no padding.

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?

All eight required parameters are schema-documented and the tool is read-only, so the description covers the essentials of what the call is for. But for a multi-constraint planning computation with no output schema, the description should indicate what result is produced (feasible allocation? shortfall?) and what the vorgaben_bestaetigt gate does — neither is explained.

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 every one of the eight parameters is already documented in the schema (remaining quantity, last used day, quantity per application, demand). The description adds no parameter-level meaning beyond that — for example, it never clarifies the relationship between je_arbeit_ml, bedarf and the two container amounts. Baseline 3 applies when the schema does the heavy lifting.

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 specific verb and resource: 'allocate whole uses from two original containers' (einplanen von ganzen Anwendungen aus zwei Originalgebinden), plus the key restriction 'without combining remnants'. That restriction distinguishes it from the sibling 'verbrauchsmittel_zweite_packung_erst_bei_luecke' and from any remnant-mixing alternative, so an agent can discriminate. It stops short of 5 because the German/English pairing leaves the precise unit of output (a plan? a feasibility verdict?) unstated.

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?

The phrase 'nach bestätigter Nutzungsfrist' implies a precondition (confirmed usage deadline), and 'without combining remnants' implies a usage constraint, so the applicable context is inferrable. However, no explicit when-to-use/when-not statement or named alternative is given, and the agent is left to decide on its own when the second-container tool is preferable.

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