Deftship MCP Server

Get / track a parcel

deftship_get_parcel

Read-only

Retrieve parcel order status, tracking number, and label URL by shipment order ID or tracking number. Use this to track shipments and poll for labels after shipping.

Instructions

Fetch a parcel order's status, tracking numbers and label URL, either by shipment_order_id or by tracking_number. Use this to poll for a label after shipping and to track a shipment. Provide exactly one of the two identifiers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deftship_get_parcel"
  }
}

Input Schema

Name	Required	Description	Default
`tracking_number`	No
`shipment_order_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context such as fetching status, tracking numbers, and label URL, and specifies the identifier constraint. No contradictions.

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 three sentences with clear structure: action, usage scenario, constraint. No unnecessary words, front-loaded with key information.

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 simple read-only tool with two parameters and no output schema, the description covers purpose, identifiers, and usage scenario thoroughly. It is sufficient for an agent to select and invoke correctly.

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 coverage is 0%, so the description provides essential meaning for the two parameters. It explains that either shipment_order_id or tracking_number can be used, and emphasizes that exactly one must be provided, adding significant value 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 verb 'Fetch' and the resource 'a parcel order's status, tracking numbers and label URL'. It specifies the two identification methods, distinguishing it from sibling tools like deftship_get_batch or deftship_get_freight, and indicates its use for polling after shipping and tracking.

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 explicitly states when to use the tool ('poll for a label after shipping' and 'track a shipment'), and provides a clear constraint ('Provide exactly one of the two identifiers'). It does not explicitly mention when not to use it or alternatives, but the sibling context implies that.

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

Deploy Server