Deftship MCP Server

Mark orders as shipped

deftship_mark_as_shipped

Mark draft orders as shipped when fulfilled outside Deftship, with optional push to your e-commerce platform.

Instructions

Mark draft orders as shipped outside of Deftship (e.g. shipped with another provider). Optionally push fulfillment back to the connected e-commerce platform. Each order is identified by id or ecommerce_id (not both).

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": {
      "orders": "<orders>"
    },
    "name": "deftship_mark_as_shipped"
  }
}

Input Schema

Name	Required	Description	Default
`orders`	Yes	Draft orders to mark as shipped.
`send_fulfillment`	No	Push fulfillment to the connected platform. Default false. Requires tracking_number and carrier.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations show readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds context that this modifies order status and optionally pushes fulfillment, which is consistent with annotations. No contradiction.

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 a single sentence plus a clarifying note, both concise and front-loaded with the core purpose.

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

Completeness5/5

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

For a tool with 2 parameters and no output schema, the description is complete. It covers when to use, required inputs, and optional behavior.

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 coverage is 100%, providing descriptions for each parameter. The description reiterates the id/ecommerce_id exclusivity but adds no new semantic information 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?

The description clearly states the tool marks draft orders as shipped outside Deftship, with a specific verb ('mark as shipped') and resource ('draft orders'). It distinguishes from sibling tools like deftship_ship_parcel by emphasizing 'outside of Deftship'.

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?

The description provides clear context for use (shipped with another provider) and specifies how to identify orders (by id or ecommerce_id, not both). However, it does not explicitly contrast with sibling tools like deftship_ship_parcel or deftship_create_parcel_order.

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

Deploy Server