Skip to main content
Glama
Sign In
mcp-ups

mcp-ups

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_locations

Find UPS Store locations, drop boxes, and access points near any address. Search by city, ZIP code, or address with optional radius and location type filters.

Instructions

Find UPS Store locations, drop boxes, and access points near an 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>"
    },
    "name": "find_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesAddress, city, or ZIP code to search near
radius_milesNoSearch radius in miles (default: 5)
location_typeNoType of UPS location to find

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral transparency. It only states 'Find' which implies a read operation, but it does not disclose the return format, potential filtering behavior, pagination, or any other operational characteristics. Lacks sufficient detail.

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 is front-loaded with the verb and resource, with no redundant or filler content. Every word contributes to the main purpose.

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?

The tool is simple, and the schema covers all parameters, but the description lacks details about the response structure or any limitations (e.g., what the returned locations include, default radius). Given no annotations and no output schema, the description is minimally adequate but could provide more context for an agent to understand what to expect.

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 baseline is 3. The description does not add extra meaning beyond the schema; 'near an address' matches the address parameter but does not elaborate on radius_miles or location_type. The schema already handles parameter documentation adequately.

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 'Find' and the resource 'UPS Store locations, drop boxes, and access points' near an address. This is specific and distinguishes from sibling tools like track_package, get_rates, and schedule_pickup, which handle different operations.

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?

The description gives clear context for when to use the tool: when searching for UPS locations near an address. It does not explicitly mention alternatives or exclusions, but the sibling set makes it obvious this is the location lookup tool, so usage is easy to infer.

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

Deploy Server

Other Tools