Skip to main content
Glama

Get USPS holiday shipping deadlines

get_usps_holiday_shipping_deadlines
Read-onlyIdempotent

The USPS recommended send-by dates for delivery before December 25 for the current holiday season, read at call time from usps.com: Ground Advantage, First-Class Mail, Priority Mail and Priority Mail Express to the lower 48 and to Alaska, Hawaii, Puerto Rico and territories; First-Class Package International, Priority Mail International and Priority Mail Express International by world region; and APO/FPO/DPO military mail by ZIP group. Includes days left from today.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_usps_holiday_shipping_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real value beyond them: data is read live from usps.com at call time (implying freshness, no cached snapshot), it is scoped to the current holiday season, and each entry includes days remaining from today — useful for reasoning about urgency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core fact (send-by dates for delivery before Dec 25, current season) is front-loaded, and the long service/region enumeration is genuinely informative rather than filler. It is a single dense sentence that is harder to scan than a short list would be, but every clause contributes scope information.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing the return value, and it does so by naming the service tiers, world regions, APO/FPO/DPO ZIP groups, and the derived days-left field. Formatting and cardinality of the response are unstated, but for a static reference lookup the agent has enough to call it correctly and know what it will get.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level clarification is needed or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: USPS recommended send-by dates for delivery before December 25, read from usps.com for the current season. It enumerates the exact service tiers and destination groupings covered, so an agent knows precisely what table this returns. It does not explicitly name the sibling tools (check_holiday_ship_by_date, get_military_mail_deadline) or contrast itself with them, which keeps it short of a 5.

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?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives. The description implies a reference lookup for current-season deadlines, but with two sibling tools covering overlapping ground (date-based checking and military mail), the agent is left to infer which one answers a given question.

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.