Canada Post MCP Server

track_parcel

Tracks a Canada Post parcel by tracking number and returns its live public status, or an honest error if Canada Post blocks the request—without inventing a status.

Instructions

Track a Canada Post parcel by tracking number. Returns the live status from Canada Post public tracking, or an honest error when Canada Post blocks the request. Never invents a status.

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

Name	Required	Description	Default
`tracking_number`	Yes	Canada Post tracking number: 16 digits, 15-digit Delivery Notice Card number, or 13-character S10 code ending in CA.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical behavior: it returns live status from public tracking, surfaces an honest error when Canada Post blocks the request, and never fabricates a status. It omits operational details such as rate limits, auth needs, or latency, which keeps it short of a 5.

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, followed by the result guarantee and the anti-fabrication constraint. Every sentence earns its place and nothing is redundant.

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 one-parameter, no-output-schema tool, the description is nearly sufficient: it covers the action, the data source, and the failure mode. It could say slightly more about what a returned status contains, but the tool's simplicity makes that a minor gap.

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 already documented with all accepted formats (16-digit, 15-digit DNC, 13-character S10 ending in CA). The description adds no meaning beyond "by tracking number," so the baseline 3 applies.

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 ("Track a Canada Post parcel by tracking number") and states what it returns (live status from Canada Post public tracking). It is clearly distinct from siblings like get_rates or find_post_office, though it never explicitly contrasts itself with them.

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 implied by "by tracking number" and the Canada Post scope, and the alternative (public tracking vs. blocking error) is described, but there is no explicit when-to-use/when-not guidance or pointer to a fallback when the request is blocked.

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

Deploy Server