Skip to main content
Glama

getecoback-climate-weather

ersatzmaterial_doppelt_reservierte_stuecke

Read-only

Gemeinsame Ersatzmaterialliste auf doppelt reservierte Einzelstücke prüfen — Detect inventory reservations that refer to the same identified pieces.

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": {
      "einzelzuordnung_belegt": "<einzelzuordnung_belegt>",
      "bestand": "<bestand>",
      "reservierung_a": "<reservierung_a>",
      "reservierung_b": "<reservierung_b>",
      "zugleich_a_und_b": "<zugleich_a_und_b>",
      "termin_gleichzeitig": "<termin_gleichzeitig>"
    },
    "name": "ersatzmaterial_doppelt_reservierte_stuecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
bestandYesEinmalig gezählter Gesamtbestand an bestätigten Stücken.
reservierung_aYesStücke mit Reservierung A.
reservierung_bYesStücke mit Reservierung B.
zugleich_a_und_bYesStücke, die in beiden Reservierungen als dasselbe Einzelstück identifiziert wurden.
termin_gleichzeitigYesWerden beide Reservierungen gleichzeitig benötigt?
einzelzuordnung_belegtYesSind Bestand und Reservierungen desselben passenden Artikels anhand gekennzeichneter Einzelstücke abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 is covered. Beyond that, the description says nothing about what the check produces — a boolean verdict, a list of conflicting pieces, or an error when inputs are inconsistent — and with no output schema that gap is meaningful for a compute-style tool taking six required numeric/boolean inputs.

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 clauses, front-loaded with the German statement followed by an English gloss; nothing is padded. The only minor cost is the bilingual duplication, which repeats rather than extends the information.

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?

For a six-required-parameter evaluation tool with no output schema, the description should at minimum say what result is returned and roughly how the inputs determine it (e.g. the role of zugleich_a_und_b versus bestand). None of that is present, leaving the agent to guess the outcome shape before calling.

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 (bestand, reservierung_a/b, zugleich_a_und_b, termin_gleichzeitig, einzelzuordnung_belegt) is already documented in the schema. The description adds no interpretation of how these values combine, so the baseline of 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?

The description names a concrete verb+object pair ('doppelt reservierte Einzelstücke prüfen' / 'Detect inventory reservations that refer to the same identified pieces'), which is more specific than the opaque German tool name. It is clear what the check is about, but it gives no differentiation from any sibling tool, so an agent cannot tell from the text alone where this check belongs in the catalog.

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?

There is no when-to-use statement, no prerequisite (e.g. that a shared Ersatzmaterialliste must exist), and no alternative named for the case where reservations are not tied to identified pieces. The agent must infer the trigger condition entirely from the tool name.

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