Deftship MCP Server

Ship freight (book BOL)

deftship_ship_freight

Destructive

Book a freight shipment using a rate ID. Charges your balance and requires confirmation. BOL and label are delivered asynchronously via webhook.

Instructions

Book a freight shipment using a rate_id from deftship_get_freight_rates. THIS CHARGES YOUR BALANCE. The BOL and label are delivered asynchronously to your token's webhook, or retrieved later with deftship_get_freight. 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_freight"
  }
}

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 freight rate id to book.

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?

Annotation destructiveHint=true is reinforced with 'THIS CHARGES YOUR BALANCE'. Description also explains asynchronous delivery and retrieval with deftship_get_freight. Does not mention voiding possibility but is otherwise transparent about charge and async nature.

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 that are entirely substantive: action, prerequisite, charge warning, async delivery method. No wasted words. Front-loaded with the most critical 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?

No output schema, but description explains what happens (asynchronous BOL and label) and how to retrieve them later. Annotations provide destructiveHint and openWorldHint. Schema is complete. Agent has all needed info to use 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 covers all parameters with descriptions (100% coverage). Description adds value by stating rate_id comes from deftship_get_freight_rates, which is not in the schema. confirm parameter is already well-documented in schema, so description adds minimal extra.

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 tool books a freight shipment using a rate_id from deftship_get_freight_rates. It specifies the resource (freight), action (book), and key input. It also distinguishes from parcel shipping by mentioning freight and referencing sibling 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 states that rate_id must come from deftship_get_freight_rates and that confirm=true is required. It implies when to use (after getting rates) and when not (for parcels, users should use deftship_ship_parcel). Lacks explicit exclusion of parcel shipping but provides strong context.

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

Deploy Server