Deftship MCP Server

Create draft freight order

deftship_create_freight_order

Create a draft freight order (visible on Open Orders page) without purchasing. Update an existing draft by passing the shipment_order_id.

Instructions

Create a draft freight order visible on the Open Orders page. Does not purchase. Returns the shipment_order_id. Pass shipment_order_id to update an existing draft.

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": {
      "pickup_date": "<pickup_date>",
      "from_opening_time": "<from_opening_time>",
      "from_closing_time": "<from_closing_time>",
      "from_address": "<from_address>",
      "to_opening_time": "<to_opening_time>",
      "to_closing_time": "<to_closing_time>",
      "to_address": "<to_address>",
      "items": "<items>"
    },
    "name": "deftship_create_freight_order"
  }
}

Input Schema

Name	Required	Description
`items`	Yes	Freight line items.
`to_address`	Yes	Receiver address (with accessorial flags).
`pickup_date`	Yes	Proposed pickup date, format Y-m-d.
`from_address`	Yes	Sender address (with accessorial flags).
`to_closing_time`	Yes	Delivery address closing time, format H:i.
`to_instructions`	No	Special instructions for delivery.
`to_opening_time`	Yes	Delivery address opening time, format H:i.
`from_closing_time`	Yes	Pickup address closing time, format H:i.
`from_instructions`	No	Special instructions for pickup.
`from_opening_time`	Yes	Pickup address opening time, format H:i.
`shipment_order_id`	No	Existing order id to update.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Discloses key behaviors: it creates a draft (not purchase), returns shipment_order_id, and can update existing drafts. Annotations already provide read/write and destructiveness info; description adds context about the return value and update capability.

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 sentences, no wasted words. Front-loaded with the main action 'Create a draft freight order'. Every sentence adds distinct information: action, non-purchase, return value, update capability.

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?

For a complex tool with 11 parameters, nested objects, and no output schema, the description is minimal but sufficient given thorough schema descriptions. It clarifies the draft nature and update path, though it omits details like date/time format requirements (handled by schema).

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

Parameters4/5

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

Schema has 100% coverage with descriptions. The description adds value by explaining that 'shipment_order_id' can be passed to update an existing draft, tying the parameter to the tool's dual behavior (create/update). This contextualizes the parameter beyond the schema.

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?

Clearly states the verb 'Create' and the resource 'draft freight order', with scope 'visible on the Open Orders page'. Distinguishes from purchasing by saying 'Does not purchase'. Differentiates from siblings like 'deftship_ship_freight' and other create tools.

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

Usage Guidelines4/5

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

Explicitly says when to use (create draft) and mentions update via 'shipment_order_id'. Implies when not to use ('Does not purchase') referencing purchase tools like 'deftship_ship_freight'. Could be more direct about alternatives.

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

Deploy Server