Deftship MCP Server

Create pickup order

deftship_create_pickup_order

Create a pickup order with carrier, addresses, and package details. Returns the order object with ID, ready for booking via arrange pickup.

Instructions

Create a pickup order visible on the Pickup Orders page. Returns the full pickup order object including its id. Use deftship_arrange_pickup to actually book it with the carrier.

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": {
      "carrier": "<carrier>",
      "pieces": "<pieces>"
    },
    "name": "deftship_create_pickup_order"
  }
}

Input Schema

Name	Required	Description
`id`	No	Existing pickup order id to update.
`pieces`	Yes	Pickup pieces.
`carrier`	Yes	Pickup carrier, e.g. 'ups', 'usps', 'dhl'.
`close_time`	No	Closing time H:i. Required for UPS.
`ready_time`	No	Opening time H:i. Required for UPS.
`pickup_date`	No	Proposed pickup date, format Y-m-d. Not required when carrier is 'dhl'.
`from_address`	No	Sender address. Required if from_address_id is not given.
`from_address_id`	No	Saved sender address id. Provide this OR from_address.

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?

The description discloses that the tool returns the full pickup order object including its id, and that it does not book the pickup. Annotations already indicate non-read-only, so the description adds valuable behavioral context beyond annotations. A slight deduction for not mentioning any error conditions or prerequisites.

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?

The description is composed of two concise and informative sentences. Every sentence adds value: the first states the action and visibility, the second describes the return value and provides a critical usage tip.

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?

Given the complexity (8 parameters, nested objects, no output schema), the description provides essential context about return value and workflow (create then arrange). It could be more complete by mentioning prerequisites like carrier setup, but it is still very informative.

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?

The schema has 100% description coverage for all 8 parameters, so the description does not need to add much. It adds no additional meaning beyond the schema, which is adequate. Baseline score of 3 is appropriate.

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?

The description clearly states the tool creates a pickup order and distinguishes it from the sibling tool 'deftship_arrange_pickup', which is used for actual booking. The verb 'Create' is specific and the resource 'pickup order' is named.

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?

The description explicitly tells when to use this tool (to create a pickup order) and when not (to actually book it, use deftship_arrange_pickup). This provides clear context and alternatives.

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

Deploy Server