hansatic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HANSATIC_API_KEY | Yes | Your Hansatic API key for accessing the packing API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pack_cargoA | Optimize how cargo is loaded into a truck, trailer or shipping container. Returns a physically valid layout (placements with x/y/z and rotation, respecting stacking, fragility, weight and axle constraints) plus the freight billing metrics: LDM (loading meters), linear feet, EUR pallet positions and total weight. Submits an async job and waits for the result — typically 5-30 seconds. Use list_vehicles first if you are unsure of the vehicle code. |
| list_vehiclesA | List all available trucks, trailers and shipping containers with their interior dimensions (mm) and max payload (kg). Use the returned codes as the "vehicle" argument of pack_cargo. |
| check_jobA | Check the status/result of a packing job by id (only needed if pack_cargo timed out on a very large manifest). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_vehicles retrieves vehicle options, pack_cargo submits an optimization job, and check_job monitors that job. There is no overlap or ambiguity.
All three tools follow a consistent verb_noun pattern with snake_case: check_job, list_vehicles, pack_cargo. The naming is predictable and clear.
With only 3 tools, the scope is narrow but well-defined. Each tool serves an essential step in the cargo packing workflow without unnecessary extras.
The domain of cargo packing is fully covered: listing available vehicles, computing an optimal pack, and checking on an async job. No obvious gaps are present.