Skip to main content
Glama

track_parcel

Read-onlyIdempotent

Build a Swiss Post tracking page URL from a parcel or registered tracking number, enabling manual status lookup when no public tracking API is available.

Instructions

Swiss Post tracking page URL for a tracking number (no live status: there is no public tracking API)

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

NameRequiredDescriptionDefault
tracking_numberYese.g. 99.00.123456.12345678 (parcel), RI 123456789 CH (registered)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / tracking_number / description
      Previous value: -"Swiss Post tracking number, e.g. \"99.00.123456.12345678\" for parcels or \"RI 123456789 CH\" for registered mail"New value: +"e.g. 99.00.123456.12345678 (parcel), RI 123456789 CH (registered)"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark it read-only, idempotent, open-world, and non-destructive. The description adds the crucial behavioral limitation that it only builds a URL and cannot return live status due to no public API. It could mention URL construction or validation details, but the key caveat is present.

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?

A single sentence, front-loaded with the output and the no-live-status limitation. There is no redundant wording.

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 one-parameter URL-builder with no output schema, the description supplies the return value and the no-live-status limitation. Nothing else is needed for an agent to call it correctly.

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 single tracking_number parameter is documented with examples in the schema. The description only restates the input concept and adds no format or validation semantics beyond what the schema already provides.

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 that it returns a Swiss Post tracking page URL for a tracking number and explicitly says there is no live status because no public tracking API exists. This is a specific output and resource, and it distinguishes the tool from a live tracking service.

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?

Makes the use case clear: construct a tracking page URL from a tracking number. It also sets the boundary that live status is unavailable, though it does not name alternatives, which is acceptable because no sibling tool appears to provide parcel tracking.

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

Deploy Server

Other Tools