Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Metric Monitor Details

get_metric_monitor_details
Read-only

Fetch a Sentry Metric Monitor's query, dataset, detection mode, thresholds, conditions, and connected Alerts to inspect configuration and verify alert settings.

Instructions

Get a Sentry Metric Monitor: its query, dataset, detection mode, thresholds, resolution conditions, and connected Alerts. Condition results: 75 critical, 50 warning, 0 resolved. Percent thresholds are absolute: 110 means 10% higher. Windows are in seconds. Connected Alerts: get_alert_rule. Cron jobs: find_monitors. URL checks: find_uptime_monitors.

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": {
      "monitorId": "<monitorId>"
    },
    "name": "get_metric_monitor_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
monitorIdYesMetric Monitor ID from find_metric_monitors, not a legacy metric alert ID.
regionUrlNo
projectSlugNoThe 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
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 and the description correctly adds domain behavior instead: how condition results are laid out (75 critical, 50 warning, 0 resolved), that percent thresholds are absolute (110 = 10% higher), and that windows are in seconds. Those interpretive rules are impossible to derive from the annotations, though nothing is said about failure behavior when the monitor ID is unknown or about caching.

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?

Purpose is front-loaded in the first clause, followed by interpretation notes and then routing hints, with no filler sentences. The telegraphic fragment style ('Windows are in seconds.') is dense but each line carries distinct information, so little is wasted.

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

Completeness5/5

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

For a read-only detail fetch with an output schema, the description covers what matters: exact scope of the resource, how to read the non-obvious returned values (absolute percent thresholds, second-based windows, condition counts), and where to go for adjacent objects. Return payload structure is correctly left to the output schema rather than duplicated.

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 80% and every parameter (monitorId, regionUrl, organizationSlug, projectSlug, fresh) is already documented in the schema, including the 'not a legacy metric alert ID' caveat. The description adds no parameter-level meaning of its own, so the baseline 3 applies; its threshold/window notes describe output rather than inputs.

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?

States a specific verb and resource ('Get a Sentry Metric Monitor') and enumerates the returned facets (query, dataset, detection mode, thresholds, resolution conditions, connected Alerts), which distinguishes it from monitors of other kinds. It does not explicitly contrast with the sibling get_monitor_details, so an agent must infer that distinction from the title alone.

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?

The trailing routing lines ('Connected Alerts: get_alert_rule. Cron jobs: find_monitors. URL checks: find_uptime_monitors.') effectively tell the agent which adjacent resource to fetch elsewhere, functioning as when-not guidance. It stops short of an explicit statement about choosing this over get_monitor_details or about legacy metric alert IDs (that caveat lives only in the schema).

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