Skip to main content
Glama

getecoback-climate-weather

verbrauchsmittel_zweite_packung_erst_bei_luecke

Read-only

Mit dokumentierter Öffnungs- und Verwendungsfrist prüfen, ob eine ungeöffnete Reservepackung gebraucht wird — Delay opening a sealed pack until a dated need exceeds usable stock.

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": {
      "verwendung_belegt": "<verwendung_belegt>",
      "angebrochen": "<angebrochen>",
      "offen_bis": "<offen_bis>",
      "reserve_inhalt": "<reserve_inhalt>",
      "reserve_geschlossen_bis": "<reserve_geschlossen_bis>",
      "reserve_nach_oeffnung_tage": "<reserve_nach_oeffnung_tage>",
      "a_tag": "<a_tag>",
      "a_stueck": "<a_stueck>",
      "b_tag": "<b_tag>",
      "b_stueck": "<b_stueck>"
    },
    "name": "verbrauchsmittel_zweite_packung_erst_bei_luecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_tagYesTag des ersten Bedarfs.
b_tagYesTag des späteren Bedarfs.
a_stueckYesMenge am ersten Termin.
b_stueckYesMenge am späteren Termin.
offen_bisYesLetzter belegter Nutzungstag für angebrochene Stücke.
angebrochenYesBestätigt nutzbare Stücke in der angebrochenen Packung.
reserve_inhaltYesBestätigte Stückzahl der ungeöffneten Reserve.
verwendung_belegtYesSind die Packungsvorgaben, die Kompatibilität und die beiden Bedarfstermine bestätigt?
reserve_geschlossen_bisYesLetzter belegter Tag für das erstmalige Öffnen der Reserve.
reserve_nach_oeffnung_tageYesZusätzlich bestätigte Höchstdauer nach Öffnung der Reserve; die äußerste Frist gilt weiterhin.

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?

readOnlyHint=true and openWorldHint=false already tell the agent this is a closed-world, side-effect-free computation, so the description is not carrying the safety burden. It adds the decision criterion (dated need vs. usable stock) and the notion that deadlines are documented, but says nothing about what the check returns or how conflicting deadlines are resolved — despite there being 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, one German and one English, with the operative constraint (Delay opening...) front-loaded. The bilingual pairing is slightly redundant but each version is tight and there is no filler.

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 10-required-parameter computational tool with no output schema, the description should say at least what result comes back (a yes/no decision, an applicable deadline, a quantity comparison). It states the question being answered but never the answer shape or the edge cases (unconfirmed documentation, reserve that would expire before use), leaving a real gap for an agent trying to interpret the response.

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 every one of the 10 required parameters carries its own German explanation, so the schema does the heavy lifting and a 3 is the baseline. The prose frames the concepts (documented opening/usage deadline, usable stock, sealed reserve) but adds no format or interaction detail — e.g. how 'a_tag/b_tag' relate to 'offen_bis' — beyond what the schema already says.

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 concrete decision task (prüfen, ob eine ungeöffnete Reservepackung gebraucht wird) tied to documented opening/usage deadlines, and the English clause restates the rule: delay opening until a dated need exceeds usable stock. That is a specific verb-plus-resource, but it never names the closely related sibling tools in this consumables family (e.g. verbrauchsmittel_zwei_originalbehaelter_einzelbedarf), so differentiation rests on the reader's inference.

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?

"Delay opening a sealed pack until a dated need exceeds usable stock" describes the decision the tool makes rather than telling an agent when to call it, when not to call it, or which sibling to prefer. Usage is implied by the domain, not stated, and the precondition signaled by the parameter 'verwendung_belegt' (are the constraints and both need dates confirmed?) is never surfaced in prose.

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