Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

container_lookup

Read-onlyIdempotent

Retrieve ISO shipping container specifications and compute load fit for items. Supports 10 container types including standard, high-cube, reefer, open-top, and flat-rack.

Instructions

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. Add item dimensions (item_length_cm/width_cm/height_cm, optional item_weight_kg and item_quantity) to also compute how many such items fit.

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 — 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoContainer slug. Examples: "20ft-standard", "40ft-high-cube", "20ft-reefer". Omit to list all 10 types.
item_quantityNoNumber of items to check against the container.
item_width_cmNoItem width in cm.
item_height_cmNoItem height in cm.
item_length_cmNoItem length in cm — provide all three item dims to get a load-fit calculation.
item_weight_kgNoItem weight in kg — caps the fit by max payload.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
resultYes
_sourceYes
citationYes
validityNo
warningsNo
confidenceYes
blocking_errorsNo
envelope_versionYes
normalized_inputNo
Behavior5/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds: 'read-only reference data', rate limits (25 req/day), 429 error behavior, and 'fit calculations are geometric best-effort — they do not model load distribution, securing or mixed cargo.' It also notes that specs are manufacturer-typical and pending verification.

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: begins with a clear summary, then details usage, behavior, limitations, and related tools. It is front-loaded with the primary purpose. While reasonably concise, a few sentences could be trimmed without losing essential info.

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?

The description covers all relevant aspects: functionality, optional parameters, error handling, rate limits, output structure, provenance, limitations, and related tools. Given the complexity (6 optional parameters, output schema exists), it provides comprehensive guidance for correct usage.

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 description coverage is 100%, so parameter details are already provided. The description adds value by explaining the 'type' slug syntax, the collective purpose of item dimensions for fit computation, and the optionality. However, it does not elaborate on each item parameter individually, which the schema already covers.

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's purpose: 'Get ISO shipping-container specifications, with optional load-fit maths.' It lists 10 specific container types and contrasts with sibling tools (e.g., validate, cbm_calculator, uld_lookup), making its distinct role unambiguous.

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?

The description explicitly explains when to omit the type parameter to list all containers, how to provide item dimensions for load-fit calculations, and what happens on unknown type errors. It also mentions rate limits and retry guidance, and provides related tools for alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SoapyRED/freightutils-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server