Canada Post MCP Server

list_mymail

List incoming Canada Post MyMail items from local mock or exported data, with an optional limit. Returns results only when opt-in settings are configured; never logs in.

Instructions

List incoming mail from Canada Post MyMail. LOCAL ONLY and OPT-IN. Returns mock sample items only when CANADA_POST_MyMAIL_ENABLED=true and CANADA_POST_MyMAIL_MOCK=true, or items from a local export file you saved yourself. Fails cleanly when not configured. Never logs in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_mymail"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum items to return. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses that no login occurs, that data is mock or from a user export, that the tool is opt-in via environment flags, and that it fails cleanly when unconfigured. It does not describe the shape of returned items or any pagination behavior, which keeps it from 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?

The core purpose is front-loaded in the first clause, followed by tight constraint sentences (local-only, opt-in gating, data provenance, failure mode, no login). Every sentence adds a non-redundant operational constraint; nothing is filler.

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 read tool with no annotations or output schema, the description covers what an agent most needs: preconditions for data being returned, data provenance, and failure behavior. The main remaining gap is the shape of the returned mail items, which is not explained anywhere.

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% and the single parameter (`limit`, default 10) is already fully documented in the schema. The description adds no further meaning such as maximum allowed value or interaction with the mock/export source, so the baseline of 3 applies.

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 a specific verb and resource: 'List incoming mail from Canada Post MyMail.' This is unambiguously distinct from the sibling tools (find_post_office, get_rates, track_parcel) and an agent can tell instantly that this lists locally-available mail items rather than querying postal services.

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?

Gives clear prerequisites for use: LOCAL ONLY, OPT-IN, and only returns items when MOCK flags are enabled or a user-saved export file exists. It doesn't name an alternative tool, but none of the sibling tools could substitute, so the implied usage context is sufficient.

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

Deploy Server