Single tool with basic structure but significant gaps. The track_shipment tool has a name that starts with a verb (✓), a description present (✓), and an input schema with type information (✓). However, the description is minimal (85 chars), lacks guidance on error cases, dependencies, and the expected output format is not documented. The input schema is minimal, only one required parameter 'reference' with minLength constraint, but no pattern/format specification, no enum values, and no description of what constitutes a valid DB Schenker reference number beyond the example '1806203236'. The output schema is completely undocumented in the visible source; callers must infer the structure from implementation details in DbSchenkerAdapter.ts, which returns a complex union type (TrackingResult) with conditional success/failure branches. Error cases are returned as object properties (ok: false, status: 'blocked', error: 'NOT_FOUND') rather than structured error responses with actionable guidance. The tool does not follow the response-field-naming pattern: response fields use inconsistent casing and structure (e.g., 'ok', 'error', 'message', 'reference', 'details', 'upstream') without clear mapping to what an LLM should extract. No pagination support despite the tool potentially returning large tracking histories. No tool annotations (readOnlyHint, etc.). Overall, this server provides bare-minimum tool structure without production-grade documentation or schema clarity.

• Document the complete output schema for track_shipment. Include both success and error branches: success returns {ok: true, reference, shipment_details: {...}, tracking_history: [{code, timestamp, location, ...}], trip_points: [{...}]}; errors return {ok: false, error: <ERROR_CODE>, message: <user-friendly description>}.
• Expand the input parameter description for 'reference': 'DB Schenker tracking reference number (8-13 digits, e.g., 1806203236). Also accepts shipment STT identifiers. Required.'
• Add a regex pattern or format constraint for the reference parameter. If valid references are 8 - 13 digits, express that as a JSON Schema pattern: '^[0-9]{8,13}$'.
• Rewrite the tool description to 150 - 200 chars, including: 'Track a DB Schenker shipment by reference number to retrieve real-time status, location, delivery milestones, and estimated delivery date. Returns shipment details, tracking history with timestamps and locations, and GPS trip points if available. Call this to answer 'where is my package?' and provide customers with delivery status.'
• Add tool annotation readOnlyHint: true to signal the tool is safe to invoke speculatively.
• Implement structured error responses with classification. For NOT_FOUND: {ok: false, error: 'NOT_FOUND', message: 'No shipment found for reference 1806203236. Verify the reference number and try again.', reference, retryable: false}. For CAPTCHA_BLOCKED: {..., retryable: true, retry_after_seconds: 60}.
• Document the CAPTCHA blocking behavior in the tool description: 'If DB Schenker temporarily blocks requests with CAPTCHA challenges, this tool returns a cached response for 60 seconds to avoid repeated failures. After 60 seconds, retry.'