Skip to main content
Glama

special_cargo

Evaluate dangerous goods, reefer, and out-of-gauge cargo for a lane, including acceptance status, surcharges, and equipment requirements.

Instructions

Assess SPECIAL / NON-STANDARD CARGO for a lane — dangerous goods, refrigerated (reefer), and out-of-gauge — the moves a plain 'dry box' rate model can't price or clear. DANGEROUS GOODS (IMDG): give a hazard class ('3', '2.1', 'class 9') or a commodity that classifies to one (e.g. 'paint' → Class 3 flammable liquid, 'lithium batteries' → Class 9), and it returns the IMDG hazard family, the STOWAGE category (on/under deck), the SEGREGATION requirements against any other classes you list in the same booking, the documentation burden (the shipper's Dangerous Goods Declaration + class-specific papers), the per-class DG SURCHARGE, and — the decision that matters — whether that class is ACCEPTED on a standard liner service, needs prior approval, or is commonly REFUSED (Class 1 explosives, 6.2 infectious, 7 radioactive). REEFER: give a commodity ('frozen shrimp', 'bananas', 'pharma 2-8') and it returns the carrying SETPOINT + tolerance band, the regime (frozen/chilled/pharma/ambient-controlled), the cold-chain RISK (a pharma GDP breach can total the cargo; a banana below 12°C is chilling injury), and the reefer plug + pharma cold-chain + controlled-atmosphere PREMIUMS. OUT-OF-GAUGE (OOG): give over-dimensions (length/width/height in cm + weight) or request a flat-rack/open-top, and it picks the equipment, computes how many neighbouring SLOTS the protrusion sterilises, the OOG surcharge (equipment + slots + lashing/survey), and the BREAKBULK fallback when nothing fits a box. Every figure is MODELED planning data — NOT the IMDG Code, a carrier DG acceptance ruling, or a certified declaration (regla 7). PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key. Same UN/LOCODE port normalization as get_spot_rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origin_portYesOrigin port (city name, UN/LOCODE, or 'City, Country').
dest_portYesDestination port (city name, UN/LOCODE, or 'City, Country').
container_typeNoContainer size '20ft'/'40ft'/'40HC'. Optional; defaults to '40ft'.
dg_classNoIMDG hazard class for a dangerous-goods check: '1','2.1','2.2','2.3','3','4.1','4.2','4.3','5.1','5.2','6.1','6.2','7','8','9' (also 'class 3' etc). Provide this OR a 'product' that classifies to a class.
other_classesNoOther IMDG classes in the same booking / on board, to evaluate SEGREGATION against. Optional.
productNoFree-text commodity. Drives the reefer lookup ('frozen shrimp', 'bananas', 'pharma 2-8') OR infers a DG class for some families ('lithium batteries' → 9, 'paint' → 3).
oog_equipmentNoExplicit out-of-gauge equipment: 'flat-rack-40','flat-rack-20','open-top-40','open-top-20','breakbulk'. Optional.
length_cmNoOver-dimension piece length in cm (triggers an OOG assessment). Optional.
width_cmNoOver-dimension piece width in cm. Optional.
height_cmNoOver-dimension piece height in cm. Optional.
weight_kgNoPiece weight in kg (drives flat-rack vs breakbulk). Optional.
reeferNoForce a reefer assessment even without a recognised product. Optional.
controlled_atmosphereNoAdd the controlled-atmosphere (CA) reefer premium. Optional.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that figures are modeled planning data, not certified, and mentions the premium payment model (x402 USDC or prepaid key). However, it does not explicitly state whether the tool is read-only or any authentication/rate limit details.

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 long but well-structured with clear sections for each cargo type. Every sentence adds value, though some redundancy exists. The length is justified by the tool's complexity.

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 13 parameters, no output schema, and no annotations, the description thoroughly covers both input usage and output expectations for all three cargo types, including the premium model and data disclaimer. It is complete for an assessment tool.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant context beyond schema descriptions: it explains how parameters interact (e.g., product inferring DG class), details output for each cargo type, and clarifies optionality. This exceeds the baseline 3.

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 defines the tool's purpose: assessing special/non-standard cargo (dangerous goods, reefer, out-of-gauge) for a lane, distinguishing it from standard dry box rate models and sibling tools like get_spot_rate. The verb 'assess' is specific and the resource ('SPECIAL / NON-STANDARD CARGO') is well-defined.

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

Usage Guidelines4/5

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

The description explains when to use the tool (for cargo that a plain dry box model can't price) and what it returns for each cargo type. It implies not to use for standard cargo (use get_spot_rate) but does not explicitly name all alternatives among siblings.

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/Baneado98/freight-pulse'

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