Deftship MCP Server

Ship a parcel (buy label)

deftship_ship_parcel

Destructive

Purchase a parcel shipping label using a rate ID from the rate lookup. Charges your account and requires explicit confirmation.

Instructions

Purchase a parcel label using a rate_id from deftship_get_parcel_rates. THIS CHARGES YOUR BALANCE. The label and tracking numbers are delivered asynchronously to your token's webhook, or retrieved later with deftship_get_parcel. Requires confirm=true.

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": {
      "rate_id": "<rate_id>"
    },
    "name": "deftship_ship_parcel"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be set to true to actually execute this action. This operation charges your Deftship balance or is otherwise irreversible. Confirm with the user before setting true.
`rate_id`	Yes	The rate id to purchase (from get-parcel-rates).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true. Description adds critical context: 'THIS CHARGES YOUR BALANCE', asynchronous delivery, and retrieval method. No contradiction with annotations.

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 concise sentences, each adding essential information. No filler, front-loaded with the main action. Every sentence earns its place.

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 moderate complexity and good schema/annotations, the description covers prerequisites, action outcome, async behavior, and post-action retrieval. Slightly more detail on rate_id source could elevate completeness, but it's already adequate.

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% and already describes both parameters. Description adds no new semantic meaning beyond the schema, merely reiterating the confirm=true requirement. Baseline 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?

Description clearly states the verb 'Purchase a parcel label' and identifies the specific resource (parcel label) and prerequisite (rate_id from deftship_get_parcel_rates). It distinguishes the tool from siblings by referencing related tools for rates and retrieval.

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 states when to use (after getting rates) and requires confirm=true. Mentions alternative retrieval via deftship_get_parcel. Does not fully elaborate on when not to use or compare to batch shipping, but provides sufficient guidance.

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

Deploy Server