Skip to main content
Glama

track_parcel

Generate Swiss Post tracking URLs to monitor parcel delivery status by entering a tracking number, then open the official page in your browser.

Instructions

Generate a Swiss Post parcel tracking URL for a given tracking number. Swiss Post does not provide a public tracking API, so this returns the official tracking page URL to open in a browser.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tracking_numberYesSwiss Post tracking number, e.g. "99.00.123456.12345678" for parcels or "RI 123456789 CH" for registered mail

Implementation Reference

  • The handler logic for the "track_parcel" tool, which constructs a tracking URL for Swiss Post.
    case "track_parcel": {
      const trackingNumber = String(args.tracking_number ?? "").trim();
      if (!trackingNumber) {
        throw new Error("tracking_number must not be empty.");
      }
    
      const trackingUrl = `https://service.post.ch/ekp-web/ui/entry/shipping/1/parcel/detail?parcelId=${encodeURIComponent(trackingNumber)}`;
    
      return JSON.stringify({
        tracking_number: trackingNumber,
        tracking_url: trackingUrl,
        note: "Swiss Post does not provide a public tracking API. This URL opens the official Swiss Post tracking page for your parcel. No authentication required to view tracking status in browser.",
        formats: "Swiss Post tracking number formats: \"99.xx.xxxxxx.xxxxxxxx\" for standard parcels (e.g. 99.00.123456.12345678), \"RI xxxxxxxxx CH\" for registered mail, \"RR xxxxxxxxx CH\" for registered parcels.",
      });
    }
  • The registration and input schema definition for the "track_parcel" tool.
    {
      name: "track_parcel",
      description:
        "Generate a Swiss Post parcel tracking URL for a given tracking number. Swiss Post does not provide a public tracking API, so this returns the official tracking page URL to open in a browser.",
      inputSchema: {
        type: "object",
        required: ["tracking_number"],
        properties: {
          tracking_number: {
            type: "string",
            description:
              "Swiss Post tracking number, e.g. \"99.00.123456.12345678\" for parcels or \"RI 123456789 CH\" for registered mail",
          },
        },
      },
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains key behavioral traits: it generates URLs rather than fetching tracking data directly, requires opening in a browser due to lack of API, and specifies the service provider (Swiss Post). It doesn't mention rate limits, authentication needs, or error handling, but covers the core operational behavior well.

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?

The description is perfectly concise with two sentences that each earn their place: the first states the core purpose, the second explains the critical behavioral constraint (no API, browser required). There's zero wasted language and it's front-loaded with the main functionality.

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 annotations and no output schema, the description provides good contextual completeness. It explains what the tool does, why it works this way (no API), and what to expect (a URL to open). It could slightly improve by mentioning the return format explicitly, but covers the essential context given the tool's simplicity.

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 description coverage is 100%, so the schema already fully documents the single parameter. The description adds marginal value by reinforcing that the tracking number is for Swiss Post and mentioning example formats, but doesn't provide additional syntax or validation details beyond what the schema specifies. This meets the baseline for high schema coverage.

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 clearly states the specific action ('Generate a Swiss Post parcel tracking URL') and the resource involved ('for a given tracking number'). It distinguishes this tool from all sibling tools, which are primarily data retrieval tools for various Swiss public services, by focusing on URL generation rather than direct data access.

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?

The description provides clear context for when to use this tool: when Swiss Post tracking is needed and no API exists, requiring a browser-based approach. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools, though the distinction is implied by the unique purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server