lashing
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_sailingsA | Sailings from one port to another, earliest arrival first, with cut-offs and a routing_reference to book. |
| get_bookingB | A booking's status, what it means, what can be done next, its route, cut-offs and equipment. Includes the carrier's latest arrival estimate once the booking is confirmed. |
| track_shipmentA | Where a shipment is: each vessel call with planned, estimated and actual times. Includes delays in hours and the latest container moves. |
| list_bookingsA | Bookings this lashing instance has created or changed, newest first. |
| list_plansA | Proposed changes that have not been applied, discarded or refused yet. |
| propose_bookingA | Prepare a new booking request. Nothing is sent until apply_plan. Party details come from the operator's config, not from you. |
| propose_changeA | Prepare a change to a booking: an update before confirmation, an amendment after. Nothing is sent until apply_plan. |
| propose_cancellationA | Prepare a cancellation of the booking, or of its pending amendment only. Nothing is sent until apply_plan. |
| apply_planB | Send a proposed plan to the carrier, once, if a grant covers it or a person approves it. |
| discard_planA | Drop a proposed plan so it can never be applied. |
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 10 tools
Each tool targets a distinct resource and action: find_sailings searches, get_booking/list_bookings read, track_shipment follows movements, propose_* creates different plan types, and apply_plan/discard_plan manage plan lifecycle. There is no meaningful overlap between read, write, and lifecycle operations.
All tool names follow a consistent verb_noun snake_case pattern with specific, descriptive verbs. The naming convention is uniform across search, retrieval, planning, and application actions.
Ten tools is well-scoped for a booking and shipment management domain. Each tool represents a distinct workflow stage without redundancy or unnecessary bloat.
The set covers the core lifecycle: search sailings, propose and apply bookings, view bookings, track shipments, propose changes/cancellations, and discard plans. Minor gaps exist, such as no dedicated get-plan-by-id tool and no explicit refusal-handling action, but the existing tools appear sufficient for normal agent workflows.