Public leaderboard

Public assessment

SoapyRED/freightutils-mcp (freightutils-mcp)

freightutils-mcp · v2.12.3 · scanned

What changed in the harness

Selection accuracy 100→100, token cost down 0%, unconfirmed writes 100%→100%.

Category breakdown

Where the score comes from.

Earned points across the four signals Gradable measures. Safety and Legibility are scored out of 30; Economics and Discoverability are scored out of 20.

01Safety

30.0 / 30

30.0 out of 30
02Legibility

27.6 / 30

27.6 out of 30
03Economics

4.5 / 20

4.5 out of 20
04Discoverability

15.1 / 20

15.1 out of 20

Highest-impact fix

Estimated gain +16 points

Reduce the tool-definition and task token payload

Consolidate overlapping tools and trim repetitive schema text while preserving behavior, parameter, and return semantics.

Description evidence

Defects and rewrites.

2 defects found across the exposed tool descriptions. Suggested rewrites make purpose, inputs, boundaries, and returns easier for an agent to understand.

Tool Defect types Suggested rewrite
container_lookup
params_unexplained
Get ISO shipping-container specifications, with optional load-fit maths. Covers 10 types: 20ft/40ft standard, 40ft and 45ft high-cube, 20ft/40ft reefer, 20ft/40ft open-top and 20ft/40ft flat-rack. Provide type as a slug (e.g. 20ft-standard, 40ft-high-cube) for one container's record; omit it to list all 10. To also compute how many items fit, supply the item's full 3D size: item_length_cm and item_width_cm define the footprint the item occupies on the container floor, and item_height_cm defines its stacking height — all three are needed for the load-fit calculation; item_weight_kg caps the fit by max payload and item_quantity is the count to check against. Behavior: read-only reference data with per-record provenance (sources, audited_at, decision_rationale); an unknown type errors with the valid slug list. Fit calculations are geometric best-effort — they do not model load distribution, securing or mixed cargo. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits. Returns: the container record — internal/external/door dimensions (cm), capacity_cbm, tare_weight_kg, max_gross_kg, max_payload_kg and euro/GMA pallet counts — plus a loading summary when item dimensions are supplied — under result, plus confidence, _source and citation (the FreightUtils v1 response envelope). Limitations: manufacturer-typical specs, provenance pending independent verification (the envelope's provenance_status says so) — actual equipment varies by lessor and line; confirm against the carrier's equipment guide. Related: validate (checks a container NUMBER's ISO 6346 check digit — not specs), cbm_calculator / consignment_calculator (the cargo volume to fill it), uld_lookup (the air-freight equivalent).
pallet_fitting_calculator
params_unexplained
Calculate how many identical boxes fit on a pallet: boxes per layer (trying 90-degree rotation when allowed), layer count within the max height, totals, volume utilisation and weight capping. Provide the pallet footprint (pallet_length_cm, pallet_width_cm) and pallet_max_height_cm (total stack height INCLUDING the pallet deck, which defaults to 15 cm via pallet_deck_height_cm). Describe the box with its full 3D size: box_length_cm and box_width_cm define the box footprint used to compute boxes per row/column on the layer (90-degree rotation is tried when allow_rotation is true), and box_height_cm determines how many layers stack within the usable height; box_weight_kg with max_payload_kg enables the weight-capping check. Behavior: deterministic geometric packing of one box size in aligned rows and columns — it does not model interlocked or mixed-orientation patterns; weight_limited reports when max_payload_kg caps the count below the geometric fit. Missing or non-positive dimensions error naming the parameter. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits. Returns: boxes_per_layer, layers, total_boxes, orientation, boxes_per_row/col, usable_height_cm, utilisation_percent, total_box_volume_cbm, wasted_space_cbm and the weight fields under result, plus confidence, _source and citation (the FreightUtils v1 response envelope). Limitations: a theoretical best-effort fit — real stacking obeys carton strength, overhang and load-stability rules it does not model. Related: ldm_calculator (pallets into trailer length), vehicle_lookup (pallet capacity per vehicle), container_lookup (pallets into containers).

Selection evidence

Confusable tool pairs.

8 pairs where similar names or overlapping descriptions may send an agent toward the wrong tool.

Tool A Tool B Confidence Why they collide
airline_lookup airport_lookup high Both tools are IATA-code lookups whose names differ only by 'airline' vs 'airport'; codes collide in practice ('BA' is both British Airways and Buenos Aires airport, 'LH' both Lufthansa and Berlin), so a task like 'look up the IATA code BA' genuinely cannot be disambiguated from the definitions alone.
cbm_calculator consignment_calculator medium consignment_calculator also computes per-line and total CBM, so a task like 'calculate the CBM of my shipment/consignment' could route to either; cbm_calculator handles a single box shape while consignment_calculator covers multi-line totals, so line-count phrasing is the only discriminator.
cbm_calculator ldm_calculator medium Both are dimension-based freight calculators denominated in 'metres' (cubic metres vs loading metres), and both take piece length/width/height; a task phrased 'calculate the metres for this cargo' or 'work out the volume in metres' is genuinely ambiguous between the two.
ldm_calculator consignment_calculator medium consignment_calculator (mode=road) also computes LDM per line with stackable handling, so a road-freight task like 'calculate the loading metres for my consignment' could plausibly pick either; only single-pallet vs multi-line intent separates them.
uld_lookup vehicle_lookup medium Both are near-identical read-only equipment-spec lookups (slug/category filters, dimensions, payload, pallet capacity) that differ only by transport mode — air ULD vs road vehicle; a task like 'look up the equipment specs and pallet capacity' with no mode mentioned is ambiguous.
chargeable_weight_calculator ldm_calculator low Both are dims+weight freight calculators sharing the word 'freight', but one is explicitly air billing weight and the other road loading metres; a vague task like 'how will I be billed for this freight' could misfire, though 'chargeable weight' and 'loading metres' phrasing normally disambiguates.
chargeable_weight_calculator pallet_fitting_calculator low Both combine dimensions and weight in a calculator ('weight' is a shared token); a task like 'calculate the weight of this pallet load' is ambiguous between air billable weight and pallet weight-capped box count, though the descriptions name distinct purposes.
adr_lq_eq_check ics2_check low Both are compliance 'check' tools over goods (dangerous-goods quantity relief vs EU ENS goods-description screening), so a task like 'check whether this consignment of goods is compliant' could plausibly route to either, even though their inputs (UN numbers/quantities vs a description) differ sharply.

Compare the field

One score is useful.
The evidence makes it actionable.

Back to the leaderboard