Skip to main content
Glama

lastscanned: Parcel & Ocean Container Tracking

Track several packages

track_packages
Read-onlyIdempotent

Track up to 100 numbers at once (at most 35 per carrier). Each entry has a result or an error; one bad number never fails the rest. Without sign-in only the first number is tracked; past a daily limit the remaining entries come back with error code auth_required or rate_limited. zipcode applies to every number whose carrier takes a postcode.

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_numbers": "<tracking_numbers>"
    },
    "name": "track_packages"
  }
}

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_numbersYes

Output Schema

NameRequiredDescriptionDefault
noticeNo
resultsYes
credits_remainingNo

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
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "credits_remaining": {
      +      "type": "integer"
      +    },
      +    "notice": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "properties": {
      +          "error": {
      +            "properties": {
      +              "code": {
      +                "type": "string"
      +              },
      +              "message": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "code",
      +              "message"
      +            ],
      +            "type": "object"
      +          },
      +          "result": {
      +            "properties": {
      +              "carrier": {
      +                "type": "string"
      +              },
      +              "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"
      +                ]
      +              },
      +              "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"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "trackingNumber": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "trackingNumber"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "results"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, and the description still adds real behavior: partial failure isolation ('one bad number never fails the rest'), anonymous truncation, and rate-limit/auth error codes per entry. It stops short of describing ordering or throttling/pagination detail, but the substantive gaps are covered.

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?

Four sentences, front-loaded with the batch caps, then failure semantics, then auth/rate-limit behavior, then the cross-entry zipcode rule. No filler and no restatement of the title.

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 shape needn't be explained, and the description still covers limits, partial failure, anonymous behavior and error codes. Nothing an agent needs to invoke this correctly is missing.

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?

Schema coverage is 67% and the description adds cross-parameter meaning the schema cannot: zipcode applies to every number whose carrier takes a postcode, and carrier may be omitted for detection. This tells the agent how one value fans out across array entries, which is the key semantic risk here.

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 plus its defining scope: batch tracking of up to 100 numbers with a 35-per-carrier cap. That batch framing plus the per-entry result/error note makes it distinguishable from the singular track_package sibling without opening any 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 concrete usage conditions — anonymous callers get only the first number tracked, and a daily limit turns remaining entries into auth_required/rate_limited errors. It does not explicitly say to use track_package when tracking a single number, so the alternative routing is left implicit.

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