mcp-ups
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| track_packageA | Track a UPS package by tracking number. Returns current status, location history, and estimated delivery. |
| get_ratesB | Get UPS shipping rates between two addresses for a package. |
| find_locationsA | Find UPS Store locations, drop boxes, and access points near an address. |
| schedule_pickupB | Schedule a UPS package pickup at your address. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct UPS operation: tracking, rate quotes, location lookup, and pickup scheduling. There is no overlap or ambiguity between their purposes.
All tools follow a clear verb_noun pattern: track_package, get_rates, find_locations, schedule_pickup. The naming is consistent and predictable.
Four tools is a well-scoped set for a UPS-focused server, covering the most common customer-facing actions without being bloated or too sparse.
The toolset covers core shipping workflows (track, rate, locate, pickup), but lacks shipment creation and pickup cancellation, which are notable but not critical gaps for typical use.