Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

list_schedules

Read-onlyIdempotent

Retrieve all PagerDuty schedules from both v2 layer-based and v3 shift-based systems in one call, with source-specific status marks for completeness.

Instructions

List ALL PagerDuty schedules across BOTH scheduling systems in a single call.

This returns classic layer-based (v2) schedules AND next-gen shift-based (v3) schedules
together. It is the complete, authoritative schedule list — there is no other list tool.
Each item's `kind` field ("layer_based" or "shift_based") says which system it belongs to.
If either source fails, `response_summary`/`sources` explicitly mark the list INCOMPLETE;
otherwise treat it as exhaustive. Never tell the user a schedule type is unsupported or missing.

Args:
    query_model: Filters (name query, team_ids, user_ids, limit). Shift-based (v3) schedules
        are filtered by name `query` and `limit` only.
    enrich: When True (default), fill in names for shift-based (v3) schedules (bounded to the
        returned page, max 50). Set False to skip the extra lookups; v3 names may then be null.

Returns:
    The merged schedule summaries with per-source status and a `degraded` flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enrichNo
query_modelYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourcesNoPer-API retrieval status for each scheduling system
degradedNoTrue if any source failed; the list is then INCOMPLETE
responseYes
Behavior5/5

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

Annotations already declare readOnly and idempotent. Description adds critical behavior: merge logic, per-source status on failure, enrich behavior, and an instruction to never claim a schedule type unsupported. No contradiction.

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?

Well-structured with overview, args, and returns sections. Slightly verbose but still clear and informative. Could be trimmed but 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?

Completely covers the tool's behavior: merge of two systems, failure handling, enrich option details, and return structure (degraded flag). Suitable for an AI agent to use correctly.

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 has descriptions for all sub-parameters (high coverage), so baseline 3. Description adds extra: query_model filters differently per schedule type, enrich fills names for v3 only and is bounded. This adds meaningful context beyond schema.

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?

Description clearly states it lists all schedules across both v2 and v3 systems, with no other list tool available. It distinguishes from siblings like get_schedule (single) and list_schedule_* (specific aspects).

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 says it's the complete authoritative list with no alternative, but does not explicitly contrast with get_schedule for single schedule retrieval. Provides usage caution about error handling and enrich option.

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