sentry-investigator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_PROJECT | No | (Optional) Your default project slug | |
| SENTRY_AUTH_TOKEN | Yes | Your Sentry API token | |
| SENTRY_ORGANIZATION | Yes | Your Sentry organization slug |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sentry_issuesC | Fetch recent issues from Sentry for investigation |
| investigate_issueC | Investigate a specific Sentry issue by analyzing the codebase and providing explanations and fixes |
| analyze_stack_traceB | Analyze a stack trace and find related code in the codebase |
| get_jira_boardsA | Get list of available Jira boards for ticket creation |
| create_jira_ticketA | Create a Jira ticket from a Sentry issue and link them together |
| get_issue_typesB | Get available issue types for a Jira project |
| create_jira_from_sentryB | Create a Jira ticket directly from a Sentry issue with automatic linking and rich context |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The set has two tools for creating Jira tickets from Sentry issues (create_jira_from_sentry and create_jira_ticket) that are nearly identical in purpose, causing ambiguity. Additionally, analyze_stack_trace and investigate_issue have some overlap in context analysis, though not exact duplicates.
Most tools follow a verb_noun pattern, but 'create_jira_from_sentry' introduces a preposition, and the two Jira creation tools use different naming structures despite similar functions, leading to inconsistency.
With 7 tools covering Sentry issue retrieval, analysis, and Jira ticket creation, the count is well-scoped for the server's purpose without being too sparse or bloated.
The tools cover the primary workflow of investigating Sentry issues and creating Jira tickets, but there are minor gaps such as missing updates to tickets or listing Jira projects, and redundancy reduces overall completeness.