Delopt delivery dispatch

Plan a driver's departure

plan_vehicle_departure

Read-only

A driver is leaving the depot now with these orders: find the best visiting sequence and each order's ETA.

The orders must fit the vehicle's capacity. To decide which orders a driver should take, use plan_deliveries instead. Nothing is stored or sent to the driver.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vehicle": "<vehicle>",
      "orders": "<orders>"
    },
    "name": "plan_vehicle_departure"
  }
}

Input Schema

Name	Required	Description
`depot`	No	Where the vehicles start from. Omit only if your API key is bound to a depot, in which case the server supplies it.
`orders`	Yes	The orders this driver is taking out.
`vehicle`	Yes	The vehicle (driver) leaving now.

Output Schema

Name	Required	Description
`stops`	Yes	In visiting order
`notice`	No	Account notice to pass on to the user, e.g. a trial ending soon
`depart_at`	Yes
`return_at`	Yes
`vehicle_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 2, 2026
- addedInput schema / $defs / OrderSpec / properties / lat / description
```
Added value: +"Latitude in decimal degrees; give with lon, or omit both"
```
- addedInput schema / $defs / OrderSpec / properties / lon / description
```
Added value: +"Longitude in decimal degrees; give with lat, or omit both"
```
- addedInput schema / $defs / Place / properties / lat / description
```
Added value: +"Latitude in decimal degrees; give with lon, or omit both"
```
- addedInput schema / $defs / Place / properties / lon / description
```
Added value: +"Longitude in decimal degrees; give with lat, or omit both"
```
- addedInput schema / properties / orders / description
```
Added value: +"The orders this driver is taking out."
```

Changed7 schema fields changedOct 24, 2026

removedInput schema / $defs / VehicleSpec

Removed value: -{
-  "properties": {
-    "available_at": {
-      "anyOf": [
-        {
-          "format": "date-time",
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "When the vehicle is back at the depot and free for a new route. Omit if it is available now.",
-      "title": "Available At"
-    },
-    "capacity": {
-      "default": 5,
-      "description": "How many orders the vehicle can carry at once",
-      "exclusiveMinimum": 0,
-      "title": "Capacity",
-      "type": "integer"
-    },
-    "id": {
-      "description": "Your reference for the vehicle or driver",
-      "title": "Id",
-      "type": "string"
-    }
-  },
-  "required": [
-    "id"
-  ],
-  "title": "VehicleSpec",
-  "type": "object"
-}

removedInput schema / properties / vehicle / $ref
```
Removed value: -"#/$defs/VehicleSpec"
```
addedInput schema / properties / vehicle / description
```
Added value: +"The vehicle (driver) leaving now."
```

addedInput schema / properties / vehicle / properties

Added value: +{
+  "available_at": {
+    "anyOf": [
+      {
+        "format": "date-time",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "When the vehicle is back at the depot and free for a new route. Omit if it is available now.",
+    "title": "Available At"
+  },
+  "capacity": {
+    "default": 5,
+    "description": "How many orders the vehicle can carry at once",
+    "exclusiveMinimum": 0,
+    "title": "Capacity",
+    "type": "integer"
+  },
+  "id": {
+    "description": "Your reference for the vehicle or driver",
+    "title": "Id",
+    "type": "string"
+  }
+}

addedInput schema / properties / vehicle / required
```
Added value: +[
+  "id"
+]
```
addedInput schema / properties / vehicle / title
```
Added value: +"VehicleSpec"
```
addedInput schema / properties / vehicle / type
```
Added value: +"object"
```

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Nothing is stored or sent to the driver', which is meaningful for an openWorldHint tool that computes ETAs. It does not say what happens if the orders exceed vehicle capacity (rejection vs. partial plan), and the non-idempotent hint is left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and result, followed by the hard constraint and the sibling routing. No wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't spell out return values, and it correctly signals that both the visiting sequence and per-order ETAs come back. What's missing is failure behavior when capacity is exceeded, which matters for a nested-object, open-world planning call.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description only restates that orders feed the sequence and must fit capacity; it adds no syntax, defaults, or depot-omission guidance beyond what the schema already documents.

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?

States a specific verb (find the best visiting sequence / ETAs) for a specific resource (this driver's orders leaving the depot now), and explicitly names the sibling it is not (plan_deliveries). An agent can distinguish it from plan_deliveries without opening either schema.

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

Usage Guidelines5/5

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

Gives both the when ('a driver is leaving the depot now with these orders') and the when-not with the alternative named ('to decide which orders a driver should take, use plan_deliveries instead'). The capacity constraint adds a precondition the agent must check before calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Delopt delivery dispatch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?