Skip to main content
Glama

Calculate Loading Metres

calculate_loading_metres
Read-onlyIdempotent

Calculates loading metres (Lademeter, LDM) -- the floor-space unit (Ladefläche) that governs European road freight -- for a list of cargo pieces, plus the equivalent number of pallet places (Palettenstellplätze, Stellplätze). Answers questions like "wie viele Lademeter" or "wieviel Platz brauche ich im Lkw".

Units: length_cm and width_cm (Länge/Breite in cm) per piece. weight_kg_per_piece (Gewicht in kg) is optional. Formula: LDM = sum(length_cm x width_cm x quantity) / reference_deck_width_cm / 100. Height is irrelevant here -- LDM is a floor-footprint metric, not a volume one (for volumetric/chargeable weight, use calculate_chargeable_weight instead).

Reference width: Lademeter (LDM) is always computed at the fixed 240cm (2.4m) reference lane -- this is a commercial road-freight convention, not a DIN/EN/ISO/VDI standard, and does not vary by vehicle. If vehicle_id names one of the loadable vehicle profiles (e.g. "semi_136" = Sattelzug 13,6 m, "rigid_75" = 7,5-Tonner), the response additionally reports deck_length_m: how much of that specific vehicle's own deck length the cargo occupies -- a different, vehicle-specific quantity, not the LDM figure. Pallet-place equivalents are also computed at the 240cm reference lane.

Worked example: 8 Europaletten/EUR-Paletten (120cm x 80cm) at the standard 240cm width = (120808)/240/100 = 3.2 LDM, equivalent to 8 Palettenstellplätze (one Europalette occupies 0.4 LDM at this width). An Industriepalette (120x100cm) occupies more floor space per unit: 0.5 LDM at the same width.

Edge cases: an unknown vehicle_id returns the list of available vehicles instead of guessing -- it never silently picks one. If any piece omits weight_kg_per_piece, total_weight_kg is returned as null rather than an incomplete partial sum. Maximum 100 piece lines (use quantity to combine identical pieces).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
piecesNoList of cargo pieces (up to 100 line items, required, non-empty). Use quantity to combine identical pieces rather than repeating rows.
vehicle_idNoOptional vehicle profile id (e.g. "semi_136" = Sattelzug 13,6 m, "rigid_75" = 7,5-Tonner). Does not change the LDM calculation (always the fixed 240cm reference lane) -- adds deck_length_m, how much of that vehicle's own deck length the cargo occupies. If given but not recognized, the response lists every available vehicle instead of guessing.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / vehicle_id / description
      Previous value: -"Optional vehicle profile id (e.g. \"semi_136\" = Sattelzug 13,6 m, \"rigid_75\" = 7,5-Tonner) to use that vehicle's real deck width instead of the 240cm standard. If given but not recognized, the response lists every available vehicle instead of guessing."New value: +"Optional vehicle profile id (e.g. \"semi_136\" = Sattelzug 13,6 m, \"rigid_75\" = 7,5-Tonner). Does not change the LDM calculation (always the fixed 240cm reference lane) -- adds deck_length_m, how much of that vehicle's own deck length the cargo occupies. If given but not recognized, the response lists every available vehicle instead of guessing."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Even with annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds rich behavioral context: unknown vehicle_id returns a list instead of guessing, missing weight yields null for total_weight_kg, max 100 piece lines, and the fixed 240cm reference width. No contradictions.

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 well-structured and front-loaded with a clear opening sentence, but it is quite long and repeats some vehicle_id behavior already present in the schema. Every sentence adds value, though the length could be slightly reduced without losing information.

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

Completeness5/5

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

Given the absence of an output schema, the description thoroughly covers all relevant return values (LDM, pallet places, deck_length_m, total_weight_kg) and edge cases. It also includes the formula, units, and a worked example, making it complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaningful semantics beyond it: the formula, worked examples, and optionality/behavior of weight and vehicle_id. While the schema already documents the fields, the description reinforces how values are used in the calculation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates loading metres (LDM) and pallet-place equivalents, with specific verb, resource, and scope. It also explicitly differentiates from calculate_chargeable_weight, making it distinct from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use the tool (floor-space questions, not volumetric weight) and names the alternative tool for volumetric/chargeable weight. Also explains when vehicle_id is relevant (to get deck_length_m).

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