MCP server for PostNord's REST APIs — track shipments, find service points, and get transit times
PostNord MCP has well-structured tool definitions with clear naming (verb_noun pattern), comprehensive descriptions (150-200 chars each), and complete input schemas using Zod validation. All four tools are READ_ONLY and properly documented. However, output schemas are not documented, LLMs cannot predict response structure for downstream planning. Parameter descriptions lack format guidance (e.g., 'Postal code format: 4 digits' for Norwegian codes). Error handling exists but lacks recovery guidance. No tool annotations (readOnlyHint) despite all tools being read-only.
Find the nearest PostNord service points (pickup/drop-off locations) by address or postal code. Returns names, addresses, opening hours, and coordinates.
Find the nearest PostNord service points (pickup/drop-off locations) by geographic coordinates (WGS84 latitude/longitude).
Estimate PostNord transit time between two postal codes for a given service code. Service codes depend on your PostNord agreement (e.g. 19 for MyPack Collect).
Track a PostNord shipment by shipment ID, item ID (parcel number), or customer reference. Returns the full tracking history with status events, estimated delivery time, and delivery details.
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting) for downstream tool chaining or data extraction. Responses are JSON-stringified but structure is opaque.
Parameter format constraints missing. 'postalCode' accepts any string; should specify format (e.g., '4 digits for NO/DK, 5 for SE/FI'). 'dateOfDeparture' lacks ISO 8601 format guidance. LLMs will pass invalid formats.
Error handling lacks recovery guidance. PostNordApiError is caught and returned as text, but no actionable hints (e.g., 'Invalid shipment ID format. Try 12-digit number + 2-letter country code'). LLMs cannot self-correct.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
Tool annotations missing. All four tools are READ_ONLY but lack readOnlyHint annotation. Agents cannot distinguish safe tools from destructive ones without explicit hints.
Parameter dependencies undocumented. find_service_points requires at least one of (postalCode, city, streetName) but this is not stated. LLMs may pass empty objects or invalid combinations.