Courier MCP

Agent readability score

Strengths

• Clear verb-based naming (e.g., 'list', 'get', 'create') aids intent identification.
• Some descriptions include specific use cases (e.g., 'used for client-side SDK auth').

Weaknesses

• Tool names like 'journey' or 'notification' lack contextual specificity.
• Descriptions often omit when to use tools, focusing only on functionality.
• Parameter details (optional/required) are inconsistently documented.

• create_journey — Vague term 'journey' without definition in description.
• list_notifications — No explanation of when to use this tool.
• replace_journey — Parameter requirements (e.g., 'exit node') not explicitly stated.

Verdict

Tools are organized but suffer from ambiguous naming and incomplete parameter documentation. The lack of explicit use-case guidance in descriptions may hinder agent decision-making, aligning with the 65/100 readability score.

9/11/2026, 2:10:46 AM

Event narrative

Server transitioned from 'auth-gated' to 'legacy' era with compliance score improving from null to 100.

Risk: medium

• 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · indicates system reconfiguration or policy update affecting access controls
• 2026-09-11T01:59:45.474Z — complianceScore increased from null to 100 · suggests successful validation of regulatory requirements after era transition

Advice

Monitor compliance score trends post-era change. Verify if 'legacy' era configuration aligns with current security policies. Check for any missing 'smokeOk' validation results that may indicate incomplete system checks.