Shipi MCP

schedule_pickup

Schedule carrier pickup for shipments by arranging collection at the shipper address. Specify carrier, date, and time for package collection.

Instructions

Schedule a carrier pickup for a shipment. The carrier will come to the shipper address to collect the package.

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": {
      "order_id": "<order_id>",
      "carrier_type": "<carrier_type>"
    },
    "name": "schedule_pickup"
  }
}

Input Schema

Name	Required	Description
`integration_key`	No	Shipi integration key
`order_id`	Yes	Order ID for the shipment
`carrier_type`	Yes	Carrier type: fedex, ups, dhl, etc.
`pickup_date`	No	Requested pickup date (YYYY-MM-DD)
`pickup_time`	No	Preferred pickup time

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Mar 18, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the action ('Schedule a carrier pickup') and outcome ('carrier will come...'), but lacks critical behavioral details: whether this is a mutating operation (likely yes), permission requirements, rate limits, error conditions, or what happens if pickup fails. For a tool with no annotations, this is a significant gap.

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?

Two concise sentences with zero waste. The first sentence states the core purpose, and the second adds useful context about the carrier's action. It's front-loaded and appropriately sized for the tool's complexity.

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

Completeness3/5

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

Given no annotations and no output schema, the description is minimal but covers the basic purpose. However, for a mutating tool with 5 parameters, it should ideally include more about behavioral traits, error handling, or output expectations. It's adequate but has clear gaps in completeness.

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 description coverage is 100%, so the schema fully documents all 5 parameters. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't clarify 'carrier_type' options or 'pickup_time' format). Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Schedule a carrier pickup') and resource ('for a shipment'), with additional context about what the carrier will do ('come to the shipper address to collect the package'). It distinguishes itself from siblings like 'create_shipment' or 'track_shipment' by focusing on pickup scheduling rather than creation or tracking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a shipment created first), exclusions (e.g., not for already picked-up shipments), or comparisons to sibling tools like 'cancel_shipment' or 'get_shipping_rates'. Usage is implied but not explicitly stated.

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

Deploy Server