mcp-ups

schedule_pickup

Schedule a UPS package pickup at your address. Provide pickup date, location, and package details to arrange collection.

Instructions

Schedule a UPS package pickup at your address.

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": {
      "address": "<address>",
      "city": "<city>",
      "state": "<state>",
      "zip": "<zip>",
      "pickup_date": "<pickup_date>"
    },
    "name": "schedule_pickup"
  }
}

Input Schema

Name	Required	Description
`zip`	Yes	ZIP code
`city`	Yes	City
`state`	Yes	State (2-letter code)
`address`	Yes	Pickup address
`pickup_date`	Yes	Desired pickup date (YYYY-MM-DD format)
`num_packages`	No	Number of packages to pick up
`total_weight_lbs`	No	Total weight of all packages in pounds

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of disclosure. It only says 'Schedule a UPS package pickup' without explaining what the user can expect after invocation—confirmation, immediate effect, required account, or potential charges. This is a significant gap for a mutation operation.

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, concise sentence that states the core purpose without any unnecessary words. It is front-loaded and to the point, with no wasted content.

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?

For a scheduling tool with no annotations, no output schema, and 7 parameters, the description is minimally viable. It conveys the action but lacks context about the result of scheduling, any side effects, or how the requested pickup will be confirmed. The schema covers parameters, but the description does not add enough behavioral or sequential context for an agent to fully understand the invocation expectations.

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?

The input schema has 100% description coverage for all 7 parameters, so the schema already documents each field. The tool description adds no parameter-specific meaning beyond what the schema provides, matching the baseline for high schema coverage.

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 action ('Schedule') and the resource ('UPS package pickup'), which is distinct from the sibling tools (track_package, get_rates, find_locations). The mention of 'at your address' adds a specific scope that matches the address parameter.

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 such as track_package or get_rates. There are no exclusions, prerequisites, or hints about typical use cases beyond the obvious action.

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

Deploy Server