No user-submitted related servers found.
Scored across 4 tools
Each tool targets a clearly distinct resource and action: parcel tracking, rate quotes, post office lookup, and MyMail inbox listing. There is no plausible overlap that would cause an agent to misselect, and the descriptions reinforce the boundaries (live API vs. recorded data vs. local mock).
All four tools follow a snake_case verb_noun pattern (track_parcel, get_rates, find_post_office, list_mymail), which is predictable and readable. The only minor deviation is list_mymail, where the object is a brand name rather than a plural noun like list_mail_items.
Four tools is on the lean side but each maps to a real, non-redundant Canada Post capability, so nothing feels padded. It only falls short of 5 because the surface is thin enough that a user might reasonably expect adjacent operations (e.g. label creation or address validation) to be present.
The set covers the read-only lookups well (tracking, rates, offices, inbox), but there is no way to create a shipment or buy a label, no postal-code/address validation, and no delivery-standard/estimated-transit lookup. These are notable gaps for a server framed as Canada Post parcel services, even if the honest-fallback design suggests intentional read-only scope.