Skip to main content
Glama

getecoback-climate-weather

ersatzteil_lieferbeleg_teilung_teilpositionen

Read-only

Bei getrennten Lieferungen festhalten, welche ausdrücklich passenden Teilepositionen zum Stichtag tatsächlich vorlagen — Reconcile two chronological delivery batches against the set required for one confirmed repair.

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": {
      "benoetigte_positionen": "<benoetigte_positionen>",
      "passend_erste": "<passend_erste>",
      "passend_zweite": "<passend_zweite>",
      "auch_in_erster": "<auch_in_erster>",
      "storno_ausdruecklich": "<storno_ausdruecklich>"
    },
    "name": "ersatzteil_lieferbeleg_teilung_teilpositionen"
  }
}

Input Schema

NameRequiredDescriptionDefault
passend_ersteYesPassende vollständige Positionen in der früheren Lieferung.
auch_in_ersterYesÜbereinstimmende Positionen, in beiden Liefersätzen vollständig vorhanden.
passend_zweiteYesWeitere passende Positionen in der späteren Lieferung, einschließlich etwaiger Wiederholung aus der ersten.
storno_ausdruecklichYesWeitere, bis zum Stichtag ausdrücklich stornierte erforderliche Positionen ohne passenden Empfang.
benoetigte_positionenYesKonkrete erforderliche und gleich gezählte Bestellpositionen.

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 establish that this is a read-only, closed-world operation, so the description need not repeat safety behavior. It adds domain context about separate deliveries, cutoff-date presence, and reconciliation against a required repair set, but does not describe return format, pagination, or what happens with inconsistent or missing data.

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?

The definition is compact and front-loads the operational context in a single German sentence followed by an English reconciliation summary. The bilingual restatement is somewhat redundant, but no sentence is clearly wasted.

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?

The tool has five required numeric parameters with full schema coverage and read-only annotations, which covers the invocation mechanics. Because there is no output schema and the description does not explain what the reconciliation returns, completeness is adequate but not fully sufficient for an agent to predict the result.

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 each of the five required numeric parameters is already documented in the input schema. The description provides thematic framing around matching positions, cutoff date, and delivery batches, but does not add parameter-level meaning beyond what the schema already provides; baseline 3 is appropriate.

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 reconciliation task: capturing which explicitly matching part positions were present for separate deliveries as of a cutoff date, against the set required for one confirmed repair. The verb/resource combination is clear enough to distinguish the operation, though it does not explicitly differentiate itself from sibling tools.

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 'Bei getrennten Lieferungen' implies the condition under which this tool is relevant, and the English sentence adds the context of two chronological delivery batches for one confirmed repair. However, there are no explicit when-not conditions, prerequisites, or named alternatives to guide selection among the many 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