ILP Drone Delivery MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_available_dronesB | Get a list of all available drones with their capabilities (capacity, heating, cooling, cost, max moves) |
| get_drone_detailsB | Get detailed information about a specific drone by its ID |
| plan_deliveryC | Plan a delivery route including cost estimate, number of moves, and drone assignment. Returns complete path planning. |
| check_drone_availabilityC | Check which drones are available to handle a delivery with specific requirements |
| get_delivery_geojsonB | Get the delivery path in GeoJSON format for map visualization. Can be used with geojson.io |
| plan_multiple_deliveriesC | Plan routes for multiple deliveries simultaneously with multi-drone optimization |
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 6 tools
Each tool has a distinct and clear purpose: checking availability, getting geospatial data, retrieving drone details, listing drones, planning a single delivery, and planning multiple deliveries. There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern (e.g., check_drone_availability, get_delivery_geojson). The naming is uniform, using snake_case throughout, which enhances readability and predictability for agents.
With 6 tools, the server is well-scoped for drone delivery operations. Each tool serves a specific function in the delivery lifecycle, from availability checks to route planning, without being overly sparse or bloated.
The tool set covers core drone delivery workflows well, including availability, details, and planning. However, there are minor gaps, such as tools for managing deliveries (e.g., canceling or updating deliveries) or handling drone status changes, which agents might need to work around.