SMKlog Parcel Shipping Rates

Track a SMKlog shipment

track_parcel

Read-onlyIdempotent

Track a shipment whose label was bought on smklog.com, by carrier tracking number: the current status, the latest scan events (newest first, up to eight) and the estimated delivery date when the carrier gives one. SMKlog labels only: not a universal tracker, so another seller's number answers not-found. Spends no quote allowance. Once a create_checkout_link session reaches label_ready, get_checkout_status hands back this number.

Parameter rules:

tracking_number is the only key; no order id or email.
It is matched after removing spaces and hyphens, ignoring case.
Typical shapes: USPS 20 to 22 digits (13 characters ending in US for international), UPS 1Z plus 16 characters, FedEx 12 to 22 digits.
Under 6 characters after cleanup: tracking_number_required. A number SMKlog never sold: 404 tracking_not_found.

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": {
      "tracking_number": "<tracking_number>"
    },
    "name": "track_parcel"
  }
}

Input Schema

Name	Required	Description	Default
`tracking_number`	Yes	Carrier tracking number from the SMKlog receipt or label page

Output Schema

Name	Required	Description	Default
`events`	Yes	Scan events, newest first, up to eight
`tracking`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 1, 2026
- changedOutput schema / properties / tracking / properties / carrier / description
```
Previous value: -"USPS, UPS or FedEx"New value: +"USPS, UPS, FedEx or DHL"
```
First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, and the description still adds material behavior: no quote allowance is consumed, scan events are capped at eight and ordered newest-first, and the not-found path returns 404 tracking_not_found. These are operational facts an agent cannot infer from the annotations or schema.

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 scope statement and the exclusion are front-loaded, and the parameter rules are cleanly bulleted with no filler. The opening sentence is long, stacking scope, return shape and event ordering into one clause chain, which slightly slows scanning but wastes nothing.

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 an output schema present, return values need not be explained, and the description still covers scope, input normalization, quota cost, and error conditions. For a single-parameter read tool this leaves nothing an agent needs missing before calling it.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema: normalization rules (spaces and hyphens stripped, case ignored), typical carrier shapes, and a minimum-length threshold that triggers tracking_number_required. An agent can pre-validate input rather than learn the rules from an error.

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?

States a specific verb and resource ("Track a shipment whose label was bought on smklog.com, by carrier tracking number") and immediately enumerates what comes back: current status, latest scan events, estimated delivery date. It also draws an explicit boundary against universal trackers, so an agent can distinguish it from any sibling 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the negative case explicitly ("SMKlog labels only: not a universal tracker, so another seller's number answers not-found") and describes the upstream path that produces the input ("Once a create_checkout_link session reaches label_ready, get_checkout_status hands back this number"). That is explicit when-to-use plus a named alternative source, which is 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.

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.