Skip to main content
Glama

getecoback-raumklima

spueler_lieferung_aufzug_nutzlast_mit_begleitung

Read-only

Bestätigte Aufzug-Nutzlast mit Lieferhülle, Hilfsmitteln und begleitenden Personen zusammen abgleichen — Include every documented load in the elevator planning check.

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": {
      "aufzug_grenze_kg": "<aufzug_grenze_kg>",
      "lieferhuelle_kg": "<lieferhuelle_kg>",
      "mitfahrende_kg": "<mitfahrende_kg>",
      "hilfsmittel_kg": "<hilfsmittel_kg>",
      "belastung_und_nutzung_belegt": "<belastung_und_nutzung_belegt>"
    },
    "name": "spueler_lieferung_aufzug_nutzlast_mit_begleitung"
  }
}

Input Schema

NameRequiredDescriptionDefault
hilfsmittel_kgYesZusatzgewicht der geplanten Lieferhilfen.
mitfahrende_kgYesZusammen bestätigtes Gewicht der vorgesehenen Personen.
lieferhuelle_kgYesGemessenes oder schriftlich bestätigtes Gesamtgewicht von Gerät und Verpackung.
aufzug_grenze_kgYesDokumentierte Nutzlast des konkret vorgesehenen Aufzugs.
belastung_und_nutzung_belegtYesSind diese Gesamtlast und Nutzung vor Ort mit dem Lieferdienst abgeklärt?

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?

The annotations already establish that this is a read-only, non-open-world operation, so the safety profile is covered. The description adds that the check uses confirmed/documented loads, but it does not disclose the outcome behavior, such as whether it returns a pass/fail result or how limit violations are handled.

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 definition is front-loaded and compact, stating the comparison target before the inclusion instruction. The bilingual phrasing adds minor redundancy, but it does not obscure the core action.

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?

For a five-parameter planning check with no output schema, the description explains what to compare but not what the tool returns or how the reconciliation result should be interpreted. It is minimally adequate, but an agent would still need to infer the output behavior.

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 input schema. The description reinforces that delivery casing, aids, accompanying persons, and elevator payload all belong in the comparison, but adds little parameter-level meaning beyond that.

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 action: reconcile confirmed elevator payload with delivery casing, aids, and accompanying persons. It clearly identifies the resource and components, though it does not explicitly distinguish this tool from sibling planning-check tools.

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?

The phrase 'in the elevator planning check' implies the context of use, and 'Include every documented load' gives an inclusion rule. However, it does not state when to choose this tool over related alternatives or when not to use it.

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