Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

get_incident_metrics_all

Read-onlyIdempotent

Retrieve full-period aggregated incident metrics from PagerDuty Analytics, including unique percentile distributions (P50, P75, P90, P95) for acknowledgment and resolution times. Filter by time range, teams, services, and urgency.

Instructions

Get full-period aggregated incident metrics from PagerDuty Analytics.

Returns rollup metrics for the entire requested period including percentile
distributions (P50, P75, P90, P95) for ack and resolve times. These percentile
fields are ONLY available from this endpoint — not from the per-team or per-service
grouped endpoints.

Args:
    created_at_start: ISO8601 DateTime. Incidents created before this are omitted.
    created_at_end: ISO8601 DateTime. Incidents created on/after this are omitted.
    team_ids: Only incidents related to these teams will be included.
    service_ids: Only incidents related to these services will be included.
    urgency: Filter by urgency: 'high' or 'low'.
    time_zone: The time zone for results (e.g. 'America/New_York').
    order: Sort order: 'asc' or 'desc'.
    order_by: Field to sort results by.

Returns:
    JSON string of AnalyticsAggregatedMetrics object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNo
urgencyNo
order_byNo
team_idsNo
time_zoneNo
service_idsNo
created_at_endYes
created_at_startYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds useful behavioral context about the aggregated nature and percentile fields, but does not cover rate limits or auth details.

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?

The description is well-structured with sections but slightly verbose. The parameter list is helpful, though it could be more concise. Overall, every part earns its place.

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?

Given the complexity (8 params, 2 required), the description covers purpose, usage guidelines, parameter semantics, return type, and differentiation. Output schema exists, so return value details are not needed. Complete.

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

Parameters5/5

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

Schema description coverage is 0%, but the description provides detailed explanations for all 8 parameters, including meaning and expected formats, fully compensating for the lack of schema descriptions.

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?

The description clearly states the tool gets full-period aggregated metrics, with specific verb and resource. It differentiates from sibling tools by highlighting the availability of percentile distributions only from this endpoint.

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 states when to use this tool vs alternatives: 'These percentile fields are ONLY available from this endpoint — not from the per-team or per-service grouped endpoints.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PagerDuty/pagerduty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server