Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

list_incident_workflows

Read-onlyIdempotent

Retrieve incident workflows with optional filters by name, limit, and additional details like steps or team.

Instructions

List incident workflows with optional filtering.

Args:
    limit: Maximum number of results to return. Maximum is 100. Default 100.
    query: Filters the result, showing only the records whose name matches the query.
    include: Array of additional details to include. Options: 'steps', 'team'.

Returns:
    List of IncidentWorkflow objects matching the query parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
includeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseYes
Behavior4/5

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

Annotations already indicate read-only and idempotent. The description adds context about the maximum limit and default value, without contradicting 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?

The description is very concise, with a clear purpose sentence and well-structured Args and Returns sections. No unnecessary words.

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?

Given an output schema exists, the description covers purpose, parameters, and return type adequately. Could mention ordering or pagination, but limit suffices.

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?

Despite 0% schema description coverage, the tool description fully explains each parameter (limit, query, include) with details like max value and allowed options, compensating completely.

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?

The description clearly states the verb 'List' and the resource 'incident workflows' with optional filtering, distinguishing it from other list tools and the singular get_incident_workflow.

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?

Usage is implied by the action of listing. No explicit when-to-use or when-not-to-use guidance is provided, which is adequate but not exemplary.

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