UPS MCP Server

Get Time in Transit

get_time_in_transit

Estimate delivery dates and transit times for UPS shipments between two locations by providing origin and destination postal codes, total weight, and optional ship date.

Instructions

Get estimated delivery dates and transit times between two locations. Returns the expected delivery date and time for each available UPS service.

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": {
      "shipFrom": "<shipFrom>",
      "shipTo": "<shipTo>",
      "weight": "<weight>"
    },
    "name": "get_time_in_transit"
  }
}

Input Schema

Name	Required	Description
`shipFrom`	Yes
`shipTo`	Yes
`weight`	Yes	Total shipment weight in lbs
`shipDate`	No	Ship date in YYYY-MM-DD format (defaults to today)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 5, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns estimated delivery dates and transit times, which implies a read operation with no side effects. However, it does not elaborate on behaviors like error handling, default values, or limitations (e.g., geographical scope). The disclosure is adequate but minimal.

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 two concise sentences that immediately convey the core purpose. Every word earns its place, with no redundancy or filler.

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

Completeness2/5

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

The tool has 4 parameters including nested objects and no output schema. The description provides no information about return format, expected values, or how to interpret results. An agent would lack essential context to correctly process the output, making the description incomplete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides descriptions for all parameters, but the tool description adds no additional meaning beyond the schema. Given 50% schema description coverage (per context signal), the description fails to compensate by explaining parameter structures, defaults (e.g., shipDate defaults to today, countryCode defaults to US), or relationships between parameters.

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 'Get', the resource 'estimated delivery dates and transit times', and the scope 'between two locations' and 'for each available UPS service'. This distinguishes it from sibling tools like track_package and get_rates.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or compare to siblings like track_package or get_rates. An agent would need to infer usage context from the tool name alone.

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

Deploy Server