Release Radar MCP by usefulapi

The three composite tools all fuse the same Sentry, PagerDuty, and GitHub data, so an agent could easily confuse incident_snapshot, oncall_handoff, and whats_broken_since_last_deploy. The descriptions do distinguish them (right-now view vs. start-of-shift briefing vs. deploy-anchored issue list), which prevents a lower score. The two low-level building blocks are clearly distinct.

All names use snake_case with a uniform release_radar_ prefix, making the set predictable. The suffix patterns vary a bit—service-led names like github_latest_deploy and sentry_recent_issues alongside narrative names like whats_broken_since_last_deploy—but the overall convention is still readable and consistent.

Five tools is well-scoped for a focused release/on-call radar. Two low-level building blocks support three composite workflows, and each tool earns its place without feeling bloated or thin.

For a read-only situational-awareness server, the surface covers deployments, Sentry issues, and PagerDuty on-call/incident context through composites. Minor gaps remain: there is no standalone PagerDuty query tool, no deployment history or multi-repo comparison, and no incident acknowledgement/management operations, but the core radar workflows are covered.