Skip to main content
Glama

AirboxShip Shipping (public)

Find Pickup Locations

find_pickup_hubs
Read-onlyIdempotent

Find nearby USPS Post Offices and Smart Lockers for package pickup/drop-off.

Returns each location's id, name, type, address and distance in miles. This is a look-up only; it does not buy a label or reserve anything.

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": {
      "location": "<location>"
    },
    "name": "find_pickup_hubs"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesAddress, place name or ZIP code, e.g. '94103' or '123 Main St, San Francisco, CA'
radius_milesNoSearch radius in miles (1 to 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds real value beyond that by enumerating the returned fields and reiterating the no-side-effect scope. It does not mention pagination, result caps, or what happens when nothing is found within the radius, leaving a small 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 short sentences, front-loaded with what the tool finds and where, followed by the return shape and the scope caveat. No sentence is redundant with another and nothing is buried.

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

Completeness5/5

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

With only two well-documented parameters and no output schema, the description supplies exactly what is missing: the returned fields and the fact that the call is read-only lookup. An agent has everything needed to invoke it correctly and interpret the response.

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%, with both location and radius_miles documented including format examples and the 1–25 bound, so the baseline is 3. The description adds no parameter-level meaning such as units, default radius behavior, or how location strings are geocoded, so it earns no credit above baseline.

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 names a specific verb and two concrete resource types ('USPS Post Offices and Smart Lockers') plus the scenario ('package pickup/drop-off'). It is unmistakably different from the siblings get_shipping_rates and track_package, so an agent can route correctly without opening a schema.

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 closing sentence gives an explicit exclusion: 'This is a look-up only; it does not buy a label or reserve anything,' which steers the agent away from using it as a purchasing step. It stops short of naming a specific alternative tool for label purchase, so it sits below the top of the scale.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources