Skip to main content
Glama

getecoback-raumklima

ersatzbestellung_nach_fund_aenderungsbedarf

Read-only

Eine bereits ausgelöste Ersatzteilbestellung nach Fund verwendbarer Teile auf Änderungsbedarf prüfen — Separate avoidable order quantities from already committed units.

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": {
      "teile_geprueft": "<teile_geprueft>",
      "gesamtbedarf": "<gesamtbedarf>",
      "neu_gefunden": "<neu_gefunden>",
      "fest_ausgeloest": "<fest_ausgeloest>",
      "offen_aenderbar": "<offen_aenderbar>"
    },
    "name": "ersatzbestellung_nach_fund_aenderungsbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamtbedarfYesGesamtmenge der betroffenen geplanten Wechsel.
neu_gefundenYesZusätzliche bestätigte und noch nicht eingeplante Teile.
teile_geprueftYesSind gefundene Teile bestätigt verwendbar und Bestellstatus sowie Änderungsrecht tatsächlich geprüft?
fest_ausgeloestYesStückzahl im Auftrag, die sich nicht mehr ändern lässt.
offen_aenderbarYesZusätzliche Stückzahl, die noch angepasst werden kann.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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, and the description's 'prüfen' is consistent with a non-mutating assessment. It adds real semantic context by defining the object of the check (trennen vermeidbarer von bereits gebundenen Mengen), but says nothing about what the caller receives back or how the committed/avoidable split is reported.

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?

A single front-loaded sentence leads with the operation and the object before the clarifying dash clause. The German and English halves partially duplicate each other, which costs a little space but does aid interpretation of the abstract term Änderungsbedarf.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only five-parameter calculation with no output schema, the definition conveys the input situation and the intended separation well, and the safety profile is covered by annotations. The remaining gap is that nothing describes the shape of the result (whether it returns a quantity, a split, or a recommendation), which matters since no output schema exists.

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 all five parameters are already documented in the schema and the baseline is 3. The description's avoidable-vs-committed framing implicitly maps onto offen_aenderbar and fest_ausgeloest, but it adds no per-parameter meaning (units, ranges, or how the boolean teile_geprueft gates the computation) beyond what the schema already states.

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?

Names a specific action (prüfen/check) on a specific resource (an already-triggered Ersatzteilbestellung) under a concrete condition (nach Fund verwendbarer Teile). The English clause sharpens the intent to separating avoidable order quantities from already committed units, so an agent can tell what the tool computes rather than merely that it 'checks' something.

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?

Usage is implied by the scenario wording ('bereits ausgelöste ... nach Fund verwendbarer Teile'), which tells the agent this applies after usable parts have been found on an existing order. There is no explicit when-not guidance, no statement of prerequisites, and no routing to an alternative tool for the case where no parts were found or no order exists.

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