SMKlog Parcel Shipping Rates

Holiday shipping deadlines

get_holiday_shipping_deadlines

Read-onlyIdempotent

The carriers’ own send-by dates for delivery by the 2026 winter holidays: USPS (Ground Advantage, Priority Mail, Priority Mail Express; delivery by Dec 25) and FedEx (Ground Economy, Ground and Home Delivery by days in transit, Express Saver, 2Day, Overnight; delivery by Dec 24), each marked on_track or too_late for today in New York, with the page each date was read from. UPS publishes no fixed dates, and the answer says so. Contiguous US only; never a guarantee and never an SMKlog estimate. No carrier call, no quote allowance.

Parameter rules:

No parameters.
After Dec 24, 2026 the answer says the season is over and lists no dates.
For a real lane and service, get_parcel_quote returns each service’s delivery estimate.

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_holiday_shipping_deadlines"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	Yes	What the dates are and are not
`today`	Yes	Today in New York (America/New_York), YYYY-MM-DD
`season`	Yes	Which season the dates are for
`carriers`	Yes	USPS, FedEx and UPS
`coverage`	Yes	Which lanes the dates are for
`season_over`	Yes	True after Dec 24, 2026; carriers is then empty

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld=false, and the description still adds substantial behavior: each date is marked on_track or too_late relative to 'today in New York', source pages are returned, results are not guarantees, and after Dec 24, 2026 the answer reports the season is over with no dates. It also clarifies that no carrier call or quote allowance is consumed, which is real operational context beyond the hints.

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

Conciseness3/5

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

The core purpose is front-loaded and dense with useful detail, but the run-on carrier enumeration plus jargon-ish fragments ('No carrier call, no quote allowance', 'never an SMKlog estimate') cost readability. Some clauses restate what the opening already established.

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?

For a no-parameter, read-only lookup with an output schema, the definition covers everything an agent needs: coverage boundaries, carrier gaps, timezone for the on_track/too_late logic, seasonal expiry, and the sibling to use for actual lane quotes. Return shape is correctly left to the output schema.

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?

Zero parameters, so baseline is 4; the description goes slightly further by devoting a 'Parameter rules' section to the absence of inputs and the time-based edge behavior. That is behavior rather than parameter meaning, so 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?

Names a specific resource (carriers' own send-by dates for the 2026 winter holidays) and enumerates the exact carrier/service coverage: USPS Ground Advantage/Priority/Express by Dec 25, FedEx Ground Economy/Ground/Express Saver/2Day/Overnight by Dec 24. It also explicitly carves out what it is not ('never an SMKlog estimate') and separates itself from sibling get_parcel_quote, so an agent can pick it without opening the 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?

Gives a clear routing rule to the alternative: 'For a real lane and service, get_parcel_quote returns each service's delivery estimate.' It also states scope limits (contiguous US only) and an exclusion (UPS publishes no fixed dates). It lacks an explicit 'use when the user asks X' trigger sentence, but the context is unambiguous.

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

All SMKlog Parcel Shipping Rates tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.