Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Uptime Monitors

find_uptime_monitors
Read-only

Find Sentry uptime monitors that check URLs over HTTP and return each monitor's URL, status, interval, owner, and project for review and filtering.

Instructions

Find Sentry uptime monitors, which check a URL over HTTP. Returns each monitor's URL, status, interval, owner, and project. Scheduled jobs (cron): find_monitors. Metric thresholds: find_metric_monitors. When more results exist, narrow by project, environment, owner, or name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_uptime_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
limitNoMaximum monitors to return.
ownerNoOwner filter: `user:123`, `team:456`, `myteams`, or `unassigned`.
queryNoText to match in the monitor name or URL.
regionUrlNo
environmentNoEnvironment to filter monitors by.
projectSlugNoThe project slug, or lowercase `all` for every project.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
monitorsYes

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, openWorldHint and destructiveHint=false, so the safety profile is structured data. The description adds value beyond that by naming the returned fields and disclosing that result sets can be truncated and how to narrow them. It does not mention the cached-read behavior exposed by the 'fresh' parameter, which is the one behavioral gap.

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 compact sentences: what it is, how it differs from the two sibling tools, and what to do when results are truncated. Front-loaded and every clause carries information; no filler.

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 an output schema present, the description does not need to explain return values, and annotations cover safety; it still handles the ambiguous cases an agent would hit (wrong sibling tool, truncated results). The only omission is any hint about caching/freshness behavior, which is minor for a read-only list 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 88%, so the schema already documents all eight parameters including formats for owner and regionUrl. The description only echoes the filter dimensions (project, environment, owner, name) without adding syntax or semantics, which is the expected baseline when the schema does the heavy lifting.

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 ('Find Sentry uptime monitors') and immediately explains what the resource is ('check a URL over HTTP'), which cleanly separates it from find_monitors (cron) and find_metric_monitors (metric thresholds). It also lists the fields each result carries, so an agent knows what it gets back.

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

Usage Guidelines5/5

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

Explicitly routes the agent: scheduled cron jobs go to find_monitors, metric thresholds go to find_metric_monitors, and this tool is for URL/HTTP checks. It additionally gives a recovery path when results are truncated ('narrow by project, environment, owner, or name'), so both selection and follow-up are covered.

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