Skip to main content
Glama

getecoback-climate-weather

ersatzteil_losbereich_an_fertigungsgrenze

Read-only

Zwei belegte Teilenummern mit getrennten Losbereichen nach gemeinsamer Herstellerskala unterscheiden — Identify a documented part branch from the model lot marker without taking a full serial number.

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": {
      "geraetelot": "<geraetelot>",
      "a_von": "<a_von>",
      "a_bis": "<a_bis>",
      "b_von": "<b_von>",
      "b_bis": "<b_bis>",
      "modell_und_ordnung_belegt": "<modell_und_ordnung_belegt>"
    },
    "name": "ersatzteil_losbereich_an_fertigungsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_bisYesLetzter einschließlicher Index für A.
a_vonYesErster einschließlicher Index, für den Teil A dokumentiert ist.
b_bisYesLetzter einschließlicher Index für B.
b_vonYesErster einschließlicher Index für Teil B.
geraetelotYesGanzzahliger Losindex aus der dokumentierten Herstellerskala, keine vollständige Seriennummer.
modell_und_ordnung_belegtYesSind Modell, beide Grenzen, Teilnummern und die einheitliche Reihenfolge der Losindizes belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 the safety profile is covered. The description adds only that a full serial number is unnecessary; it says nothing about what happens when the A and B lot ranges overlap, what the modell_und_ordnung_belegt gate does when false, or what the call returns — notable given there is 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?

It is a single compact sentence with the operative constraint front-loaded. The German/English duplication is mildly wasteful but short enough not to bloat the definition.

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 decision tool with no output schema, the description leaves the return value, the overlap/ambiguity behavior, and the role of the boolean evidence gate entirely unexplained. An agent can form the call but cannot anticipate the result or failure modes.

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 is already documented, which sets the baseline at 3. The description contributes a little extra meaning by framing the lot indices as sitting on a shared manufacturer scale and the two ranges as belonging to two documented part numbers, but adds no format or edge-case semantics beyond that.

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 a verb ("unterscheiden"/"Identify") and an object ("Zwei belegte Teilenummern mit getrennten Losbereichen"/"documented part branch"), so the general intent is discernible. However, the bilingual phrasing is muddled and the tool's actual output (a branch selection? a verdict?) is never stated, and nothing distinguishes it from the many sibling ersatzteil_* 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 clause "without taking a full serial number" hints at a precondition, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative among the large set of sibling part tools. An agent must infer the calling context entirely.

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