Imported from Ntainersco/ntainers-mcp-plugin (
skills/cargowise-lookup/SKILL.md). Install upstream withnpx skills add Ntainersco/ntainers-mcp-plugin --skill cargowise-lookup. Copyright stays with the author.
CargoWise lookup
When to use
- A user names a freight reference (
S00446739,C00133045, a house or master bill, a container number) and wants its detail. - A user asks what shipments are arriving this week, which consol a house is on, or who the consignee is.
- A user asks about an organisation or staff code in CargoWise.
These tools read the NTainers store, which is populated from the customer's CargoWise tenant. They do not call CargoWise live. Reads are fast and safe to repeat.
Choosing a tool
| You have | Call |
|---|---|
| Nothing specific — need to discover types | object_catalog_list |
| Search criteria (dates, ports, status, partial reference) | object_search |
| An exact reference and you know the type | shipment_get, consol_get, order_get, cfs_get, tbc_get, invoice_get, customs_get, booking_get |
| An exact reference but not the type | object_get |
| An organisation or staff code | cargowise.store.org.search, cargowise.store.org.get, cargowise.store.staff.search, cargowise.store.staff.get |
cargowise.store.* is the equivalent store surface (cargowise.store.search, cargowise.store.get, cargowise.store.shipment.get). Either family is fine; do not call both for the same question.
Rules
- Search before guessing. If the reference does not resolve, use
object_search. - The API key defines the tenant. Never ask for a tenant, client, or organisation ID, and never pass one. A key may be restricted to organisation codes, so an empty result can mean "not visible to this key".
- A consol is not a shipment. Consols (
C…) carry houses; shipments (S…) carry packing lines and commercial detail. - Report what the store says. If a field is empty, say it is not populated.
Freshness
Results reflect the last sync from CargoWise. If the data looks stale, see the cargowise-sync skill.