Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

get_incident_workflow

Read-onlyIdempotent

Retrieve details of a specific incident workflow using its ID.

Instructions

Get a specific incident workflow.

Args:
    workflow_id: The ID of the incident workflow to retrieve

Returns:
    IncidentWorkflow details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier for the incident workflow
nameYesA descriptive name for the Incident Workflow
selfNoThe API show URL at which the object is accessible
teamNoIf specified then workflow edit permissions will be scoped to members of this team
stepsNoThe ordered list of steps that execute sequentially as part of the workflow
summaryNoA short-form, server-generated string
html_urlNoA URL at which the entity is uniquely displayed in the Web app
created_atNoThe timestamp this Incident Workflow was created
is_enabledNoIndicates whether the Incident Workflow is enabled or not
descriptionNoA description of what the Incident Workflow does
Behavior2/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds no extra behavioral context such as permissions, rate limits, or response handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately short but uses a docstring format with 'Args' and 'Returns' sections that add minimal value. It could be more concise.

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

Completeness3/5

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

Given the low complexity (1 parameter, output schema exists), the description is just adequate. It does not explain return values or error cases, but the output schema covers that.

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

Parameters2/5

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

With 0% schema description coverage, the description merely restates 'The ID of the incident workflow to retrieve,' adding no deeper meaning or constraints beyond the schema property name.

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 'Get a specific incident workflow,' using a specific verb and resource. It distinguishes from sibling tools like 'list_incident_workflows' and 'get_incident' by specifying a single workflow.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or comparisons to other incident-related tools.

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