Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Delete Cron Monitor Environment

delete_monitor_environment
DestructiveIdempotent

Delete one environment permanently from a Sentry cron monitor while keeping the monitor and other environments; an absent environment counts as success.

Instructions

Delete one environment from a Sentry cron monitor, irreversibly. The monitor and its other environments are kept; an absent environment counts as success. To find the monitor and exact environment name, use find_monitors or get_monitor_details.

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>",
      "monitorSlug": "<monitorSlug>",
      "environment": "<environment>"
    },
    "name": "delete_monitor_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionUrlNo
environmentYesExact environment name to delete. Preserve whitespace and casing.
monitorSlugYesMonitor slug or GUID.
projectSlugYesThe project slug. In `org/project` notation, the part after the slash.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
successYes
environmentYes
monitorSlugYes
projectSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description still adds real substance: the deletion is irreversible, sibling environments survive, and an absent environment is treated as success — the last point makes idempotent behavior concrete rather than abstract. It adds no auth or permission context, which keeps it below a 5.

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?

Two sentences, zero padding. The destructive scope is front-loaded in the first clause, with the non-destructive side effects and the not-found semantics immediately after.

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, a rich annotation set, and 80% schema coverage, the description needs only to cover semantics the structured data cannot express, and it does: irreversibility, retention of other environments, and absent-environment success. What remains, such as permission requirements, is minor for this scope.

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 80%, with environment exactness, whitespace/casing preservation, and regionUrl sourcing all already documented in the schema. The description reinforces 'exact environment name' and points at lookup tools, but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 a precisely scoped resource: deleting one environment from a Sentry cron monitor, not the monitor itself. The phrasing 'The monitor and its other environments are kept' distinguishes it clearly from whole-monitor deletion siblings such as delete_metric_monitor and delete_uptime_monitor.

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 find_monitors or get_monitor_details to resolve the monitor and the exact environment name, which are hard prerequisites here. It does not state when a caller should prefer deleting the whole monitor instead, so it stops short of full when-not guidance.

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