Skip to main content
Glama

getecoback-climate-weather

verbrauchsmittel_charge_bis_klaerung_sperren

Read-only

Zur Prüfung zurückgelegte Packungskennungen vom nutzbaren Bestand getrennt führen — Exclude held and untraceable consumables when checking immediate coverage.

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": {
      "charge_lesbar": "<charge_lesbar>",
      "nutzbar_bestaetigt": "<nutzbar_bestaetigt>",
      "prueflos": "<prueflos>",
      "kennung_unlesbar": "<kennung_unlesbar>",
      "bedarf_jetzt": "<bedarf_jetzt>"
    },
    "name": "verbrauchsmittel_charge_bis_klaerung_sperren"
  }
}

Input Schema

NameRequiredDescriptionDefault
prueflosYesGetrennte Stücke mit klärungsbedürftiger Kennung.
bedarf_jetztYesTatsächlich vorgesehener Bedarf vor Ende der Klärung.
charge_lesbarYesSind die Kennungen der als bestätigt gezählten Stücke eindeutig und dem Produkt zugeordnet?
kennung_unlesbarYesWeitere Stücke mit nicht mehr zuordenbarer Kennung.
nutzbar_bestaetigtYesStücke außerhalb der Klärfälle mit bestätigter Passung und Zustand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety profile is covered. Beyond that the description adds little behavior: it does not say what is produced, whether held items can be released again, or how quantities interact (e.g., whether prueflos and kennung_unlesbar are summed and subtracted). For a five-required-parameter tool with no output schema, this is thin.

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?

It is short and front-loaded, which is good, but the two halves are the same statement in German and English, so half the text is redundant. There is no wasted length, but also no information hierarchy that would help an agent parse the concept.

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?

Five required numeric/boolean parameters and no output schema mean the description must explain what comes back, and it does not — an agent cannot tell whether the result is a filtered stock figure, a boolean coverage verdict, or a breakdown. For a rule-evaluating tool with interacting max-500 counts, the definition leaves the core semantics unexplained.

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 parameter already carries a clear German description of its meaning and bounds (0-500). The description adds no per-parameter guidance — no explanation of how bedtime counts relate to one another or how charge_lesbar affects the other four — so the baseline of 3 applies.

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 on a specific resource (separating held/untraceable package identifiers from usable stock when checking immediate coverage), which is more than a restatement of the name. However, the German clause is opaque and the English clause merely paraphrases it, so an agent still cannot tell whether this computes a coverage figure, mutates stock, or just classifies counts. The verb is not concrete enough to distinguish it cleanly from the many similarly named sibling scenario tools.

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 cue is 'when checking immediate coverage', which gives a context but no when-to-use/when-not-to-use rule and no alternative named. Nothing indicates how this differs from siblings such as verbrauchsmittel_zwei_originalbehaelter_einzelbedarf or verbrauchsmittel_zweite_packung_erst_bei_luecke, which operate on overlapping consumable scenarios.

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