Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Uptime Monitor Details

get_uptime_monitor_details
Read-only

Retrieve a Sentry uptime monitor's URL, interval, thresholds, status, and recent HTTP check results to diagnose availability and failures.

Instructions

Get a Sentry uptime monitor: its URL, interval, thresholds, status, and recent HTTP check results (status code, duration, failures). Request bodies are never returned; sensitive headers are redacted. Scheduled jobs (cron): find_monitors. Metric thresholds: find_metric_monitors. Related issues: search_issues with uptime_rule:.

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": {
      "projectSlug": "<projectSlug>",
      "uptimeMonitorId": "<uptimeMonitorId>"
    },
    "name": "get_uptime_monitor_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoAbsolute end time. Requires start; not with period.
freshNoBypass cached reads.
startNoAbsolute start time. Requires end; not with period.
periodNoRelative time range for recent checks, such as 24h or 7d. Defaults to 24h without start and end.
regionUrlNo
checkLimitNoMaximum recent checks to include.
projectSlugYesThe project slug. In `org/project` notation, the part after the slash.
uptimeMonitorIdYesUptime monitor ID from find_uptime_monitors.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
checksYes
monitorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious output behavior: 'Request bodies are never returned; sensitive headers are redacted', which tells an agent not to expect full HTTP payloads. No mention of rate limits or error behavior when the monitor is missing, keeping it below the top score.

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?

Three short lines: what is returned, then type-disambiguation routing, then a pointer to related issues. Content is front-loaded with the richest information first, and no sentence is redundant with the annotations or schema.

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?

An output schema exists, so return-value structure needn't be spelled out, yet the redaction note still adds real value, and annotations cover the safety profile. With 9 parameters at 89% schema coverage, the main remaining gap is behavior on missing monitors or on empty check history, which is minor for a read-only detail tool.

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

Parameters3/5

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

Schema description coverage is 89%, so the schema already documents start/end/period, checkLimit bounds, fresh, and regionUrl. The description doesn't explain the interplay of period vs start/end for check results, though the mention of 'recent HTTP check results' loosely ties to those filters. Baseline 3 applies when the schema carries the parameter burden.

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

Purpose4/5

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

The description opens with a specific verb+resource ('Get a Sentry uptime monitor') and enumerates the payload an agent gets back: URL, interval, thresholds, status, and recent HTTP check results. It clearly demarcates uptime monitors from cron monitors and metric monitors. It does not explicitly contrast itself with the sibling list tool find_uptime_monitors, leaving the single-vs-list distinction to the required uptimeMonitorId parameter.

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?

Explicit routing is given for adjacent resource types: 'Scheduled jobs (cron): find_monitors' and 'Metric thresholds: find_metric_monitors', plus a pointer to search_issues with uptime_rule:<id> for related issues. The path to discover the ID (find_uptime_monitors) appears only in the schema, not in the description, so the when-to-use guidance is clear but not exhaustive.

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