Skip to main content
Glama

getecoback-climate-weather

ersatzteil_mengenabgleich_einzelpackung_rueckbehalt

Read-only

Ungeöffnete, unterschiedlich große Ersatzpackungen nach Mindestreserve gezielt aufzählen — Select as few whole sealed packs as needed for a verified reserve.

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": {
      "packungsinhalt_belegt": "<packungsinhalt_belegt>",
      "klein_anz": "<klein_anz>",
      "klein_inhalt": "<klein_inhalt>",
      "gross_anz": "<gross_anz>",
      "gross_inhalt": "<gross_inhalt>",
      "ziel": "<ziel>"
    },
    "name": "ersatzteil_mengenabgleich_einzelpackung_rueckbehalt"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesMindestreserve in Einzelstücken, die zugeordnet werden soll.
gross_anzYesVerfügbare große Packungen.
klein_anzYesVerfügbare kleine Packungen.
gross_inhaltYesEinzelstücke je großer Packung.
klein_inhaltYesEinzelstücke je kleiner Packung.
packungsinhalt_belegtYesSind alle Packungen verschlossen und für dieselbe dokumentierte Variante passend?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety is covered. The description adds genuine behavior: only sealed packs count, and the selection minimizes the number of whole packs rather than filling by any order. It still never says what comes back (pack counts by size? a residual? a failure when the reserve cannot be met) 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.

Conciseness3/5

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

Short and front-loaded, but the German sentence and the English sentence carry the same content, so roughly half the text is duplication. No waste beyond that, and the operational core is placed first.

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/boolean parameters, no output schema, and the description says nothing about the result shape or edge cases (insufficient stock, unusable packs, ziel=0). For a computation-style tool whose entire value is the returned allocation, this leaves the agent guessing at what a successful call yields.

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 coverage is 100%, so every parameter is already documented with bounds and units. The description only echoes the semantic frame (two pack sizes, a target reserve, sealed packs) without adding meaning such as how ties between small and large packs are broken or how a false packungsinhalt_belegt is treated. Baseline 3 applies.

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?

States a concrete operation: enumerate whole sealed replacement packs of differing sizes and choose the fewest needed to satisfy a minimum reserve. The verb+resource is identifiable and the 'as few packs as needed' clause pins down the selection policy. No sibling is named or contrasted, so differentiation is left to 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?

Applicability is only implied: 'Ungeöffnete' (unopened) and 'verified reserve' signal that the packs must be sealed and the same documented variant, matching the packungsinhalt_belegt precondition. There is no explicit when-to-use/when-not statement and no pointer to any alternative tool for other reserve 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