Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

get_responder_load_metrics

Read-onlyIdempotent

Retrieve per-responder load metrics including on-call hours, incident and acknowledgment counts, and sleep-hour interruptions for workload analysis.

Instructions

Get aggregated load metrics per responder from PagerDuty Analytics.

Returns per-responder on-call hours, incident count, acknowledgment count,
sleep-hour interruptions, and engaged time. Use for responder workload analysis.

Args:
    date_range_start: ISO8601 DateTime. Incidents with created_at before this value are omitted.
    date_range_end: ISO8601 DateTime. Incidents with created_at >= this value are omitted.
    team_ids: Only incidents related to these teams 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 ListResponseModel containing AnalyticsResponderLoad objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNo
urgencyNo
order_byNo
team_idsNo
time_zoneNo
date_range_endYes
date_range_startYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate readOnly and idempotent; the description adds value by disclosing the specific metrics returned (on-call hours, incident count, etc.), which is useful behavioral context beyond annotations.

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?

Description is efficiently structured: a one-sentence summary, a bullet list of returned fields, and an Args section with terse parameter descriptions. No redundant or missing information.

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 presence of an output schema and annotations, the description sufficiently covers the tool's purpose, parameters, and use case. The listing of returned fields adds completeness without duplicating schema.

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

Parameters4/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 clear parameter meanings (e.g., date_range_start excludes incidents before this value). It covers all 7 parameters, though lacks allowed values for some (e.g., urgency only implies 'high'/'low').

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 identifies the tool as retrieving aggregated load metrics per responder from PagerDuty Analytics, specifying exact metrics (on-call hours, incident count, etc.) and the use case (workload analysis). It distinguishes from siblings like get_incident_metrics_* which are incident-focused.

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

Usage Guidelines3/5

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

The description states 'Use for responder workload analysis', implying usage context, but does not explicitly mention when not to use or identify alternatives among sibling tools (e.g., get_responder_metrics).

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