Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Cron Monitors

find_monitors
Read-only

Find Sentry cron monitors to track scheduled jobs through check-ins, returning status, schedule, owner, project, and recent environment state.

Instructions

Find Sentry cron monitors, which track scheduled jobs through check-ins. Returns each monitor's status, schedule, owner, project, and recent environment state. Uptime URL checks: find_uptime_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_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
limitNoMaximum monitors to return.
ownerNo
queryNo
regionUrlNo
environmentNo
projectSlugNo
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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the returned fields and the fact that results are capped rather than paged ("When more results exist, narrow by..."), but does not discuss cache behavior for the `fresh` flag or rate limits.

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?

Three short, front-loaded sections: purpose, sibling routing, and fallback strategy. The telegram-style sibling lines are dense and scannable, though the return-field list is the least information-dense sentence given an output schema exists.

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 needn't explain return values, and it still covers purpose, alternatives, and a read-narrowing strategy for a tool with 8 optional parameters. Minor gap: no explanation of how `regionUrl`/`organizationSlug` pair with `find_organizations` in practice, though the schema handles that.

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 coverage is only 38%, so the description should compensate, and it partially does by naming project, environment, owner, and name as narrowing dimensions. However it never touches `fresh`, `limit`, `regionUrl`, or `organizationSlug`, and adds no syntax detail beyond what the schema already documents for `owner` and `query`.

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 cron monitors") and immediately qualifies what they are (scheduled jobs tracked through check-ins), which separates them from uptime and metric monitors in the very next line.

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?

Explicitly routes the agent to the two nearest siblings with a labeled mapping ("Uptime URL checks: find_uptime_monitors. Metric thresholds: find_metric_monitors.") and adds a result-volume tip. It stops short of stating preconditions or exclusions (e.g., what to do for one-off issue searches), so a 4 rather than a 5.

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