No user-submitted related servers found.
Scored across 3 tools
Each of the three tools targets a different external service (Jira, GitHub Actions, Sentry) with an unambiguous, non-overlapping purpose. There is no realistic scenario in which an agent would confuse retrieving a Jira ticket with fetching CI runs or Sentry issues.
All three tools follow the same get_<source>_<resource> snake_case pattern (get_jira_ticket, get_github_actions_runs, get_sentry_issues). The convention is predictable and self-describing, so an agent can guess a tool name from its intent.
Three tools is at the thin end for a server framing itself as a 'context bridge' — each tool earns its place, but the surface is narrow. A single tool per integration means there is no fallback or alternative granularity, making it borderline under-scoped.
Read-only retrieval across three sources is coherent, but the surface has notable gaps for the stated purpose: only Actions runs (no PRs, commits, or issues), only unresolved Sentry issues (no detail or resolution filtering), and no pagination/filter parameters documented. Agents assembling cross-source context will hit dead ends quickly.
