Skip to main content
Glama

lastscanned: Parcel & Ocean Container Tracking

Track a package

track_package
Read-onlyIdempotent

Current status, estimated delivery and full scan history of one tracking number. A carrier that needs the recipient's postcode answers postcode_required until zipcode is passed.

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

Input Schema

NameRequiredDescriptionDefault
carrierNoCarrier id (see list_carriers). Omit to detect it from the number.
zipcodeNoThe recipient's postcode, for carriers that only show a parcel with it (PostNL; list_carriers names them under zipcode). Omit it unless you have it or a lookup answered postcode_required. For a parcel going abroad put the destination's two-letter country code first, e.g. BE-2000.
tracking_numberYesTracking number or shipping container number, e.g. 1Z999AA10123456784 or MSKU7812341

Output Schema

NameRequiredDescriptionDefault
eventsYesScan history, newest first
noticeNo
statusYes
carrierYes
messageNo
serviceNo
signedByNo
deliveredAtNo
destinationNo
trackingNumberYes
deliveredAtLocalNo
credits_remainingNo
estimatedDeliveryNo
statusDescriptionNo
estimatedDeliveryAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / zipcode
      Added value: +{
      +  "description": "The recipient's postcode, for carriers that only show a parcel with it (PostNL; list_carriers names them under zipcode). Omit it unless you have it or a lookup answered postcode_required. For a parcel going abroad put the destination's two-letter country code first, e.g. BE-2000.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / tracking_number / description
      Previous value: -"Tracking number, e.g. 1Z999AA10123456784"New value: +"Tracking number or shipping container number, e.g. 1Z999AA10123456784 or MSKU7812341"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "carrier": {
      +      "type": "string"
      +    },
      +    "credits_remaining": {
      +      "type": "integer"
      +    },
      +    "deliveredAt": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "deliveredAtLocal": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "destination": {
      +      "properties": {
      +        "city": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "country": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "state": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "estimatedDelivery": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "estimatedDeliveryAt": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "events": {
      +      "description": "Scan history, newest first",
      +      "items": {
      +        "properties": {
      +          "code": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "localTime": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "location": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "status": {
      +            "enum": [
      +              "label_created",
      +              "in_transit",
      +              "out_for_delivery",
      +              "delivered",
      +              "exception",
      +              "returned",
      +              "unknown"
      +            ],
      +            "type": "string"
      +          },
      +          "timestamp": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "message": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "notice": {
      +      "type": "string"
      +    },
      +    "service": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "signedBy": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "enum": [
      +        "label_created",
      +        "in_transit",
      +        "out_for_delivery",
      +        "delivered",
      +        "exception",
      +        "returned",
      +        "unknown"
      +      ],
      +      "type": "string"
      +    },
      +    "statusDescription": {
      +      "type": "string"
      +    },
      +    "trackingNumber": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "carrier",
      +    "trackingNumber",
      +    "status",
      +    "events"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description still adds real behavioral value by disclosing what a call returns (status, estimated delivery, scan history) and by describing the postcode_required signal loop, which no annotation conveys.

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?

Two tight sentences led by the payload contents, with the operational caveat second. The phrasing 'answers postcode_required' is slightly awkward, but no sentence is wasted.

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?

An output schema exists, so return values need not be enumerated further, and the description plus schema plus annotations cover the essentials for a read-only lookup. The only gap is the absence of explicit sibling routing, which is minor for a single-package lookup.

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 coverage is 100% and the carrier and zipcode descriptions already cover auto-detection and the postcode_required rule, so the description largely restates structured data. It reinforces the zipcode dependency but adds no format or syntax detail beyond the schema.

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?

The description names a specific verb and resource — status, ETA and scan history for a single tracking number — and the phrase 'one tracking number' implicitly separates it from the plural track_packages. It never names a sibling explicitly, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by 'one tracking number'; there is no explicit when-to-use versus track_packages or get_rates. The one genuine usage rule given is the postcode_required condition, which covers a single edge case rather than the tool's overall role.

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