Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Alert Options

get_alert_options
Read-only

Lists available options for Sentry alerts—notification actions, trigger/filter conditions, and sources—with config schemas to use when creating or updating alert rules.

Instructions

List what a Sentry Alert (notification workflow) can use: notification actions and integrations (Slack, Teams, email, PagerDuty) with their config schemas, trigger and filter conditions, or monitor and issue-stream sources. Use the results in create_alert_rule or update_alert_rule. Slack and Teams take channel names; Discord needs a channel ID or URL. Choices for dynamic Sentry App fields are not listed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "get_alert_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
limitNoMaximum options to return in this page.
queryNoSources only: Sentry monitor search, such as name:latency or workflow:123.
cursorNoNext cursor from the same section and filters.
sectionYes`actions`: integrations and action config schemas. `conditions`: condition types and comparison schemas. `sources`: monitors and project issue streams to connect.
regionUrlNo
actionTypesNoAction types to include, such as slack, msteams, email, or pagerduty. Only with `actions`.
projectSlugNo
sourceTypesNoMonitor types to include, such as issue_stream (all issues in a project) or metric_issue. A source with no project covers all projects. Only with `sources`.
conditionGroupNoRequired with `conditions`: workflow_trigger for Alert triggers, action_filter for action group filters.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
actionsNo
sectionYes
sourcesNo
conditionsNo
inputGuideNo
nextCursorYes
conditionGroupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: that dynamic Sentry App field choices are absent from results, and that identifier formats differ per integration (Slack/Teams channel names vs Discord channel ID or URL). It stops short of describing pagination/cursor semantics, which the schema carries instead.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool returns, then downstream usage, then the per-integration gotchas and the one limitation. No filler and every sentence contributes actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, an output schema, and full annotations, the description covers the essentials an agent needs to pick a section and reuse results correctly. Minor gaps remain around how `section` interacts with filters like actionTypes/sourceTypes and around cursor paging, but these are documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high at 82%, so the baseline is 3. The description still adds meaning beyond the schema by explaining how the returned identifiers must be formatted for Slack, Teams, and Discord, which the schema does not state. The `section` semantics are largely duplicated from the schema's own enum descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('List what a Sentry Alert ... can use') and then enumerates the three option categories: notification actions/integrations, trigger and filter conditions, and monitor/issue-stream sources. This makes clear it returns option metadata rather than alert rules themselves, distinguishing it from get_alert_rule and find_alert_rules without needing either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use the results in create_alert_rule or update_alert_rule' explicitly names the downstream consumer and the workflow this tool feeds. It also flags a real exclusion ('Choices for dynamic Sentry App fields are not listed'), but does not state when to prefer this over inspecting an existing rule via get_alert_rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.