Skip to main content
Glama

getecoback-climate-weather

geraet_verpackungsmass_datenblatt_abgrenzen

Read-only

Bei einem Platzvergleich sicherstellen, dass Maße des ausgerichteten Geräts statt Versandkartons oder ungeprüfter Händlermaße verwendet werden — Separate unpacked operating dimensions from carton measurements before a buying shortlist.

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": {
      "fach_breite_cm": "<fach_breite_cm>",
      "mass_cm": "<mass_cm>",
      "dimensionsquelle": "<dimensionsquelle>",
      "erforderlicher_freiraum_cm": "<erforderlicher_freiraum_cm>",
      "freiraum_belegt": "<freiraum_belegt>"
    },
    "name": "geraet_verpackungsmass_datenblatt_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
mass_cmYesAbgelesene Breite in Zentimetern.
fach_breite_cmYesBreite am geprüften vorgesehenen Platz in Zentimetern.
freiraum_belegtYesFreiraum und Messrichtung aus der konkreten Anleitung abgeglichen?
dimensionsquelleYesAuf die Angabe zutreffender Kontext.
erforderlicher_freiraum_cmYesFür diese Seite belegte Summe der zusätzlichen Freiräume in Zentimetern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 safety is covered structurally. The description adds the constraint that measurements must come from the aligned/checked device rather than packaging, but says nothing about what the tool does with conflicting inputs (e.g. when dimensionsquelle=verpackung) or what the result signals.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses, but the German and English halves restate the same instruction rather than front-loading new information, and the leading prepositional phrase buries the actual intent. It is compact but somewhat redundant.

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?

Five required parameters are fully documented in the schema and there is no output schema, so the description need not cover return values. Still, for a five-parameter validation tool with no annotations on semantics, it should say what a successful call yields (a verdict, a comparison, a rejection) — that is missing.

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 the parameters are already documented. The description's mention of carton vs. dealer vs. aligned-device measurements loosely frames the dimensionsquelle enum but adds no meaning beyond what the enum values and field descriptions already provide.

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 conveys the domain of the check — separating unpacked operating dimensions from carton/dealer measurements for a space comparison ("Platzvergleich") — but never states a concrete action or verb. It reads as a rule the tool enforces rather than a statement of what the tool computes or returns, and does not distinguish itself from siblings such as geraet_wahl or angebote_gesamtpreis_vergleichen.

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?

"Bei einem Platzvergleich" and "before a buying shortlist" give a usage context, which is more than nothing. However, no alternatives are named and no exclusions or preconditions are stated, so the agent must guess when to call this instead of adjacent comparison tools.

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