Skip to main content
Glama

getecoback-raumklima

ersatzteile_unterstuetzte_alternativen_zuordnen

Read-only

Zwei vorrätige Teile auf Bedarfsposten mit unterschiedlicher belegter Passung verteilen — Preserve scarce interchangeable equipment parts for tasks with no supported alternative.

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": {
      "bestaende_geprueft": "<bestaende_geprueft>",
      "flexibel": "<flexibel>",
      "nur_a": "<nur_a>",
      "a_vorrat": "<a_vorrat>",
      "b_vorrat": "<b_vorrat>"
    },
    "name": "ersatzteile_unterstuetzte_alternativen_zuordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nur_aYesBedarfsposten mit exakt einem Teil A und ohne belegte Alternative.
a_vorratYesVerwendbare unbenutzte Teile A.
b_vorratYesVerwendbare unbenutzte Teile B.
flexibelYesBedarfsposten, die je ein Teil A oder B verwenden dürfen.
bestaende_geprueftYesSind Teilekennungen, Stückzahlen und die eingetragenen Freigaben geprüft?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe closed-world operation. The description adds allocation intent and a scarcity-preservation criterion, but does not explain the return result or how assignment decisions are surfaced.

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 description is compact and front-loads the operation, followed by a short preservation rationale. The bilingual phrasing is somewhat redundant but not verbose enough to obscure the purpose.

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 schema and annotations cover inputs and safety well, and the description gives the allocation goal. However, with no output schema, the description should say more about what the read-only allocation returns or how the result is represented.

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 all five required parameters are documented in the schema. The description mentions two available parts and differing documented fit, but adds no syntax, constraints, or parameter-level meaning beyond what the schema already provides.

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 operation: distributing two available parts to demand items with differing documented fit, while preserving scarce interchangeable parts. It is understandable without opening the schema, though it does not explicitly distinguish itself from any sibling tool.

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 only implied through the preservation goal for tasks with no supported alternative. There is no explicit when-to-use, when-not-to-use, or named alternative tool guidance.

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