Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Cron Monitor Details

get_monitor_details
Read-only

Retrieve a Sentry cron monitor's schedule, status, owner, environments, recent check-ins, and check-in stats to diagnose missed or failed scheduled jobs.

Instructions

Get a Sentry cron monitor (scheduled job): schedule, status, owner, environments, recent check-ins (missed, failed, timeout, OK), and check-in stats. Uptime URL checks: find_uptime_monitors. Metric thresholds: find_metric_monitors. Issues for a monitor: search_issues with monitor.slug:.

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": {
      "monitorSlug": "<monitorSlug>"
    },
    "name": "get_monitor_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
freshNoBypass cached reads.
startNo
periodNo
regionUrlNo
environmentNo
monitorSlugYesMonitor slug or GUID.
checkInLimitNoMaximum recent check-ins to include.
includeStatsNoInclude aggregate check-in stats for the selected time range.
rollupSecondsNo
projectSlugOrIdNoProject slug or numeric ID, to pick between monitors that share a slug.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
statsYesAt most 10 most recent stat buckets, oldest first. Null when includeStats is false.
monitorYes
checkInsYes
environmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and open-world, and the description adds substantive content beyond that by naming what is retrieved (recent check-in outcomes plus aggregate stats). It does not mention caching or the effect of the fresh flag, and with an output schema present the return-field list is partly redundant, but the behavioral picture is solid.

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

Conciseness4/5

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

Four short, front-loaded sentences with no filler; the core purpose comes first and the sibling routing follows. The terse colon-and-arrow routing style is efficient, if slightly telegraphic in the closing lines.

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

Completeness3/5

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

Output schema and annotations cover the return shape and safety profile, so the description needn't explain those. For a 12-parameter, open-world tool, however, it leaves the time-range and org/region mechanics entirely to the schema, which covers only half the parameters.

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

Parameters2/5

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

Twelve parameters with only 50% schema coverage, and the description adds no parameter-level guidance beyond loosely hinting at check-ins, stats, and environments. It says nothing about the period-vs-start/end mutual exclusion, the org/region coordination between organizationSlug and regionUrl, or when to disambiguate monitors with projectSlugOrId.

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?

States a specific verb and resource ('Get a Sentry cron monitor (scheduled job)') and enumerates the returned facets: schedule, status, owner, environments, recent check-ins, and check-in stats. It explicitly distinguishes itself from find_uptime_monitors and find_metric_monitors, which cover the other monitor types.

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?

Gives clear routing rules for adjacent needs: uptime checks go to find_uptime_monitors, metric thresholds to find_metric_monitors, and per-monitor issues to search_issues with monitor.slug:<slug>. It lacks an explicit 'use this when you need a single cron monitor's detail' framing, but the alternatives are concrete enough for selection.

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