Skip to main content
Glama

Swiss Post parcel tracking link

track_parcel
Read-only

Generate the official Swiss Post tracking URL from a parcel or registered-mail shipment number; open the returned link on Swiss Post to view status.

Instructions

Generate the official Swiss Post tracking URL for a shipment number (parcels, registered mail). Returns the link; tracking status itself requires the Swiss Post site.

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_numberYesSwiss Post shipment number, e.g. '99.60.126xxx.xxxxxxxx' or 'RX...CH'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely non-redundant context: the output is a link only, and no status data is fetched. That prevents an agent from expecting tracking results, though it says nothing about URL format or failure behavior for invalid numbers.

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?

Two short sentences, front-loaded with the action and capped by the key limitation. Nothing is wasted or repeated from the schema.

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?

For a single-parameter tool with no output schema, the definition covers what the tool produces and what it does not do. Only minor details, such as handling of malformed numbers, are absent.

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 parameter already carries example formats ('99.60.126xxx.xxxxxxxx', 'RX...CH'). The description only adds that both parcels and registered mail numbers are accepted, which is marginal beyond the schema 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?

The description names a specific verb and resource ('Generate the official Swiss Post tracking URL') and immediately scopes it away from actual tracking ('Returns the link; tracking status itself requires the Swiss Post site'), so an agent can tell it is a URL builder, not a status lookup.

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?

It gives clear context: use it for a shipment number covering parcels and registered mail, and implicitly states the excluded use case (checking live status requires the Swiss Post site). It stops short of naming a sibling alternative, so not a full 5.

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