Skip to main content
Glama

getecoback-climate-weather

ersatzteil_service_offene_positionen_lieferbeleg

Read-only

Fehlende und ungeklärte Positionen einer Herstellerliste für eine Teileanfrage getrennt zählen — Reconcile documented required part lines for an existing appliance.

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": {
      "positionen": "<positionen>",
      "vorhanden_bestaetigt": "<vorhanden_bestaetigt>",
      "vorhanden_unklar": "<vorhanden_unklar>",
      "liste_bestaetigt": "<liste_bestaetigt>"
    },
    "name": "ersatzteil_service_offene_positionen_lieferbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionenYesBenötigte Positionen der konkreten angefragten Herstellerliste.
liste_bestaetigtYesZur exakten Modellvariante passende Liste bestätigt?
vorhanden_unklarYesPhysisch vorhandene Positionen mit ungeklärter Teilenummer oder Menge.
vorhanden_bestaetigtYesPositionen mit richtiger Ausführung und vollständiger Stückzahl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety profile is covered. The description adds that missing and unclear positions are counted separately, which hints at the output logic, but it does not explain dependencies such as how 'liste_bestaetigt' affects the result or what happens when counts exceed the required positions.

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 two compact sentences with the core scoping ('Fehlende und ungeklärte Positionen ... getrennt zählen') front-loaded. The bilingual repetition is slightly redundant but does not obscure the intent.

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?

With four required, fully documented parameters and no output schema, the description should clarify what gets returned (e.g., two separate counts) and how the 'liste_bestaetigt' flag influences the computation. It gestures at separate counting but remains incomplete for an agent to predict the exact 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%, so each parameter is already fully documented in the schema. The description adds no additional meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 resource (positions of a manufacturer list for a parts request) and an action (count separately / reconcile), but the phrasing 'Fehlende und ungeklärte ... getrennt zählen — Reconcile documented required part lines' is ambiguous about whether it returns counts, comparisons, or a reconciliation status. It does not clearly distinguish itself from the many sibling tools, none of which are named.

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 explicit when-to-use guidance, no when-not-to-use conditions, and no reference to an alternative tool. The agent must infer context solely from the one-line purpose statement.

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